Mobile app development for Swiss businesses

When a Swiss business needs an app

Many Swiss companies start with a good mobile website and move to an app when they need repeat use: bookings, member cards, field-service tools, ordering, or a customer portal that people open weekly. If visitors come once a year, a website is cheaper and easier to find. If they come every week, an app earns its cost.

Our comparison of PWA vs native app explains how to decide before you commit budget.

Choosing the approach

Most Swiss business apps fit the first two rows. We say so plainly in the quote, and we do not recommend a native build unless the feature list demands it.

Swiss details inside the app

• Three languages. The interface follows the phone's language, with a manual switch in settings. Strings are stored in language files, so adding Italian later does not touch the code.
• Payments. Apps that sell physical goods or services can use a payment provider that supports TWINT, cards and invoices. Rules for digital goods follow Apple's and Google's billing policies, which we check per case.
• Formats. CHF amounts, four-digit postcodes, Swiss phone numbers and the date format set per language.
• Privacy. Both stores ask you to declare what data the app collects. Apple publishes this as privacy labels and Google calls it the data safety section. The revised Federal Act on Data Protection, in force since 1 September 2023, also expects an accurate privacy notice.
• Login. Email plus a one-time code, or sign-in with Apple or Google, with account deletion inside the app, which both stores expect.

Accessibility matters too. Large text settings, screen readers and good contrast are expected on both platforms, and Swiss public bodies and larger firms increasingly ask for them in tenders. We test with the built-in accessibility tools on real devices.

What moves the price of an app

Most apps start with a first release that does one job well. A second release adds the features users ask for. This keeps the first quote small and lets real usage guide the next steps.

Store listings and launch

We prepare the App Store and Google Play listings in each language, with screenshots, descriptions and keywords researched per language. Apple's review guidelines and Google Play's developer policies change often, so we check them at the time of submission. You publish under your own developer accounts, which keeps ownership clean. Budget two weeks of buffer for review rounds.

After launch we monitor crashes, release updates and plan the next iteration. A small maintenance plan is quoted separately.

Working across the time gap

We work remotely. Switzerland is 3.5 to 4.5 hours behind India. Planning calls usually sit between 09:00 and 12:00 in Switzerland, which is early afternoon in India, and test builds are shared through TestFlight and Google Play internal testing so your team can try each sprint on real phones. You get a demo every week and one lead for questions.

Pricing

Projects start at $1,500, and the hourly rate is $30. A simple companion app is a small project, while an app with accounts, payments, an admin panel and several languages is larger. The fixed quote lists screens, features and what is out of scope. You may also need a backend, covered in web app development. Our mobile app service page lists the standard deliverables.