Online booking for small businesses: your own app or a platform?

What a booking platform and an app under your own name cost over time, what Apple and Google require, and why the choice depends on your needs.

Also available in Français · Deutsch · Italiano

Your clients already book online, through a platform that sends reminders and sometimes takes a deposit. Then a supplier offers you "your" app, or a competitor announces theirs, and the question comes up: do you need your own? There is no answer that suits every business. It comes down to your actual needs: how often your clients come back, what your trade sells, who should keep the client file, and the budget you can set aside for it each year.

What a booking platform does well

A booking platform is quick to set up. There is nothing to develop: the online diary, the reminders and often deposit payments are ready to go, and the supplier handles the updates. Some also make you visible to people who did not know you before.

If what you mainly need is an online diary with reminders, because you are starting out or your clients book twice a year, a platform can cover that need entirely, and for a long time.

What a platform costs over time

The price comes in two forms, sometimes both at once: a subscription, or a commission on each booking or each payment. What can change afterwards matters more.

  • Prices and terms. You accept them as they are, and they change. Faced with a price rise, your only lever is to leave.
  • The client relationship. Your client opens an account with the platform and gets their reminders from it. The name they see most often is not yours.
  • The client file. Names, numbers, history: it all sits with the supplier. The question is whether you can get it back, and for how long after cancelling.
  • Visibility, in both directions. Look at what a client sees after booking with you: your business only, or other addresses near them too?

The test. Open your platform's admin area today, find the client file export and run it. You should get a file your spreadsheet can open, with names, contact details and appointment history. If the feature does not exist, or only exports names, you know what you would lose by leaving.

The test. Reread the terms and conditions and look for three passages: how the price can be changed and with how much notice, how quickly you can cancel, and what happens to your data afterwards. Can't find them? Put the question to support in writing.

What an app in your own name brings

Your own app puts your logo on your clients' phones:

  • Reminders and notifications, sent in your name. Apple sets a limit: notifications must not be used for promotions or direct marketing unless the client has opted in within the app and can opt out later (guideline 4.5.4 of the App Review Guidelines). An appointment reminder is fine; this month's offer needs consent.
  • Payment by TWINT or card. A haircut, a physio session or a driving lesson is consumed outside the app. For these services, Apple requires a payment method other than in-app purchase (guideline 3.1.3(e)), and Google prohibits using its billing system for physical services, gym memberships included (Google Play Payments policy). So you take payment through your own payment provider.
  • What is specific to your trade: packs of ten lessons, monthly memberships, punch cards, loyalty cards, booking with a particular member of staff.
  • The client file with you, or with a provider you have chosen under contract.

Publishing an app: what Apple and Google require

The Apple Developer Program costs 99 dollars per membership year, shown in local currency when you enrol. Google Play charges a one-time registration fee of 25 dollars. The rest takes more preparation.

The account must be yours. Apple rejects apps created from a commercialised template or app generation service, unless they are submitted directly by the provider of the content (guideline 4.2.6). The provider of the content is you. Ask from the outset for the app to be published from your own developer account.

A company or a person. To enrol an organisation, Apple requires a D-U-N-S Number, the business identifier issued free of charge by Dun & Bradstreet. Allow up to five business days to obtain it, then two for Apple to receive it. Google will not create an organisation account without a valid D-U-N-S Number either. Apple also requires a public, working website on a domain associated with the business: a social media page is not enough. Above all, Apple only enrols legal entities as organisations. Sole proprietors enrol as individuals, and their personal name appears as the seller. A hairdresser running a sole proprietorship will therefore see her own name under the app, not the salon's.

Health practices. Google requires an organisation account for health apps, medical apps included (choose a developer account type). Apple requires apps that provide services in highly regulated fields, health included, to be submitted by the legal entity that provides those services, not by an individual developer (guideline 5.1.1(ix)).

A real app. Apple expects features, content and a user interface that go beyond a repackaged website. An app that is not particularly useful or lacks anything app-like does not belong on the App Store (guideline 4.2). Your website wrapped in an app shell risks rejection.

A privacy policy. Both stores require one, with a link in the listing and within the app itself (guideline 5.1.1(i) at Apple, User Data policy at Google). You also have to declare what data the app collects, third-party tools included: the privacy details at Apple, the Data safety section at Google.

An app needs updating every year

Apple and Google raise their technical requirements regularly.

  • Since 28 April 2026, apps submitted to Apple must be built with Xcode 26 and the iOS 26 SDK (Apple's requirements).
  • Since 31 August 2026, new apps and updates submitted to Google Play must target Android 16, with a possible extension until 1 November. An existing app that does not target at least Android 15 is no longer offered to new users whose phone runs a more recent version of Android (target API level).

At Google, the deadline already fell at the end of August in 2025. So plan for someone each year to rebuild, test and republish, and ask for the cost of that upkeep in writing before you sign.

Data protection: what the revFADP requires either way

The Federal Act on Data Protection (revFADP) applies whatever the tool. Four points matter.

  • Processing by processors (Art. 9 FADP). The provider that stores your appointments processes the data on your behalf. It needs a contract, it may only do what you would be entitled to do yourself, and you must ensure that it guarantees data security. The FDPIC makes the point on its page on outsourcing: you remain responsible, and the processor may not process the data for its own purposes.
  • Disclosure abroad (Art. 16). If the data leaves Switzerland, the country concerned must offer a level of protection the Federal Council considers adequate. Otherwise, safeguards are required in principle, for example standard data protection clauses.
  • The duty to inform (Art. 19). When data is collected, your clients must be told at least your identity and contact details, the purpose of the processing, any recipients, and the name of the country if the data goes abroad. The privacy policy the stores require is the practical way to do this.
  • Health data. The law classes it as sensitive personal data (Art. 5). Physiotherapists, osteopaths, psychologists and their auxiliary staff are also bound by professional confidentiality (Art. 321 of the Swiss Criminal Code), and Art. 9 FADP only permits processing by a processor if no duty of confidentiality prohibits it. Ask the provider what it can see of your diary, and where it stores it.

It all depends on your needs

Neither option is better in itself. Five questions help pin down what your business actually needs.

  1. Do your clients come back often? An app mainly serves those who keep it on their phone: the client who returns every five weeks, the learner driver who books lesson after lesson. If your clientele is mostly passing trade, online booking already covers that need.
  2. What do you sell besides time slots? Lesson packs, memberships, punch cards, several staff members each with their own diary. If your platform handles all of this properly, it meets that need. If you keep a spreadsheet on the side, your needs go beyond what it offers.
  3. Do you want to attract new clients or keep your regulars coming back? A platform can show you to people who do not know you yet. An app reaches those who have installed it, so clients who already know you. The two needs can coexist.
  4. Who should keep the client file? Run the export test. If you get everything back, in a readable format, the question is settled. If not, weigh up what that file is worth to your business.
  5. What budget can you plan for over several years? On one side, the subscription or commissions, which can go up. On the other, development, the yearly update and the developer account. Compare the two over the same period.

Depending on your answers, the balance will tip towards a platform, an app or a combination of the two. Your needs change as your business does: go through these questions again when it evolves.

This article describes the law as it stood at the time of writing and does not constitute legal advice.
Let's work together

Got a project?
Let's talk.

Message us on WhatsApp