Exclusively
Log In
AppointmentsManage bookings and clientsWebsitesEdit and manage your websiteCustomer HelpTroubleshooting and support
Book a Call
ExclusivelyBook a Call
← All articles

App Store Guidelines for Salon Apps: What Apple and Google Require

App Store Guidelines for Salon Apps: What Apple and Google Require

Salon owner testing booking app before submission

A salon app has to clear two separate reviews before clients can download it: Apple’s App Review and Google Play’s. Both check that the app is complete, stable and honest about the data it collects. Both also expect you to give reviewers a working login. Most rejections come from preventable gaps, not from anything unusual about salons. This guide covers the accounts, assets, rules and tests that matter for a barbershop, salon, suite or beauty studio app.

Getexclusively
Give Your Salon App a Branded Home
Exclusively brings custom websites, mobile apps, booking systems, and payment solutions together for beauty professionals seeking a consistent online presence.
Visit Exclusively

TL;DR

  • Apple charges US$99 per membership year for its developer program, and you need a developer account with each store before you can submit.
  • Reviewers need a finished app with working support and privacy-policy links, accurate screenshots and demo login credentials, since a salon app almost always has accounts.
  • Apple says crashes, placeholder content and incomplete information (guideline 2.1) account for over 40% of unresolved issues.
  • Any app that lets clients create an account must also let them delete it from inside the app.
  • New personal Google developer accounts must run a closed test with at least 12 testers for 14 days before applying for production access.

Table of Contents

How the two stores differ for a salon app

The stores are not interchangeable. Apple reviews every submission by hand against its published guidelines. Google Play asks you to complete a set of declarations in Play Console, then reviews the app against its policies. Plan for both from the first day, because the paperwork you prepare for one covers most of the other.

Area Apple App Store Google Play
Developer account Apple Developer Program, US$99 per membership year Play Console developer account
Build you upload Signed iOS distribution build (.ipa) to App Store Connect Signed Android App Bundle (.aab) to Play Console
Pre-release testing TestFlight Internal, closed and open testing tracks
Privacy Privacy details in App Store Connect plus a privacy policy link Privacy policy plus the Data safety form
Reviewer access Demo credentials and access notes in App Review Information Active demo account and login details for review
Extra hurdle Strict review of completeness and “web wrapper” apps Closed test for new personal accounts

The account fee comes from Apple’s membership page. Apple says it applies per membership year, or the local-currency equivalent where available. The upload format comes from Expo’s documentation, which explains that an iOS build goes to App Store Connect and an Android bundle goes to Google Play Console. A debug build or a simulator build will not do.

Accounts and assets to prepare before you submit

Most delays happen before anyone presses “Submit”. Gather this list first.

Developer accounts

You need an Apple Developer Program membership and a Google Play developer account. Register them under the business name, not a freelancer’s personal account. The app’s seller name appears on the listing, and a client looking at a barbershop’s app expects to see the barbershop’s name there. It also keeps you in control if a designer or agency moves on.

Listing information

Apple says you must provide metadata for your product page: the app name, icon, description, screenshots, previews and keywords. You also complete the age rating questionnaire and the privacy details in App Store Connect. Google asks for the same kind of accurate app information, plus your privacy policy and Data safety answers, as laid out in its Play Console requirements.

For a salon app, that means:

  • Name and subtitle: the business name first. Add a short descriptor such as “Book appointments” if it fits. Do not stuff in city names or competitor terms.
  • Description: what clients can do (book, reschedule, pay, join a membership), described in the same terms the app uses.
  • Screenshots: real screens from the finished app, showing the booking flow, a provider’s services and prices, and the confirmation. Apple lists inaccurate screenshots among the common problems, so do not show features the app does not have.
  • Support URL and privacy policy URL: both must load. Apple asks for working links, and a dead support page is one of the quickest ways to a rejection.

Reviewer access

This is the item salon owners forget. If clients need to log in to book or pay, the reviewer does too. Apple asks for valid demo credentials and any special access instructions, and its guidance on providing information for a complete review repeats the point for account-based features. Google likewise wants an active demo account and login information among the resources for review.

Create a demo client account with a few upcoming appointments, a saved service and, if you sell memberships, an active plan. Make sure it does not expire, and do not use a real client’s data. If payment is part of the flow, write down exactly how the reviewer can test it without charging a real card.

The review guidelines that matter most to salon apps

Apple’s App Review Guidelines are long, and most of them concern games, social networks and other categories. A booking app for a barbershop touches a small set of them. Here is where to focus.

Completeness and stability

Apple’s own review guidance says an app should be stable, complete, free of placeholder content and functional as advertised. It names crashes, broken links, incomplete review information and inaccurate screenshots as common problems. It also says that over 40% of unresolved issues relate to guideline 2.1, which covers crashes, placeholder content and incomplete information.

In practice: no “Lorem ipsum” bio on a barber profile, no “coming soon” tabs, no buttons that lead nowhere. If you have not set up gift cards yet, hide the gift card tab rather than ship an empty one.

Apps that are only a website in a frame

Apple flags limited web-wrapper experiences and apps with insufficient lasting value as review problems. A salon app that simply shows your website inside a shell is at risk. A native app that handles booking, push notifications, saved payment methods, appointment history and memberships is a different thing, because it gives clients a reason to keep it on their phone. If you are choosing how to build, native iOS and Android apps under your own brand are built to this standard.

Original work

Apple says apps can be removed and developers expelled for copying another developer’s work. This matters if you are tempted to clone a template and swap the logo. Your name, icon and screens should be your own, and the same template used by dozens of businesses with no differentiation invites scrutiny.

Accounts and deletion

Apple requires that apps supporting account creation also offer an in-app path for account deletion. A client who signed up to book a fade must be able to delete that account from the app’s settings, without emailing you. If the app supports Sign in with Apple, Apple’s guidance says to revoke the user’s tokens with its REST API when an account is deleted.

Privacy and local law

A salon app collects names, phone numbers, email addresses, appointment history and sometimes payment details. Apple’s guidelines say developers are responsible for understanding the laws on data collection, storage and privacy in every location where the app is available. Google says your privacy policy and in-app disclosures must comprehensively disclose how the app collects, uses and shares user data, including the types of parties it is shared with.

That last phrase matters if you use a payment processor, an email tool or analytics. Each one is a party that receives data, and the Data safety form and Apple’s privacy details should name what they receive. Laws differ by country and state, so if you serve clients outside the US, check the rules where they live or ask a privacy lawyer. Our own processing terms are public: see Square payment processing terms and Stripe payment processing terms.

Privacy and local law — overview diagram

Google Play’s extra step for new accounts

Google requires personal developer accounts created after November 13, 2023 to run a closed test before they can publish. The test needs at least 12 testers opted in continuously for at least 14 days, and only then can you apply for production access.

Twelve testers complete fourteen-day closed test

That is a calendar problem, not a technical one. If you plan a launch around a holiday weekend or a grand opening, start the closed test weeks earlier. A barbershop has an easy tester pool: staff, regulars you trust, and family. Ask them to install from the test link, book an appointment and leave the app installed for the full period. Check Google’s current page for exact conditions, since the rule applies to personal accounts and Google may adjust it.

A submission checklist you can follow

  1. Open both developer accounts under the business name.
  2. Finish the app and remove every placeholder, test button and unfinished tab.
  3. Build signed release versions: an .ipa for Apple and an .aab for Google. Debug builds are rejected.
  4. Write the listing: name, icon, description, keywords, screenshots from the real app.
  5. Publish your privacy policy and support page on live URLs, and make sure the policy matches what the app actually collects.
  6. Complete the forms: Apple’s age rating and privacy details, Google’s Data safety and content rating declarations.
  7. Create the demo account and write the reviewer notes.
  8. Test through TestFlight and Play testing tracks on real devices.
  9. Add in-app account deletion.
  10. Submit, answer reviewer questions quickly and fix whatever they flag.
  11. Release using each store’s release controls once approved.

The overall flow, from accounts through TestFlight and Play testing to release controls, matches the submission walkthrough published by Expo. Expo documents the upload tooling, but the review rules come from Apple and Google themselves.

What to test before you press submit

Apple’s guidance points at crashes and bugs, so test on more than your own phone. Cover at least one older iPhone, one recent iPhone, a mid-range Android phone and a larger Android phone if you can borrow them.

Run these salon-specific flows end to end:

  • Book, reschedule, cancel. Do it as a new client and as a returning one.
  • Provider choice. If your shop has several barbers with their own prices and hours, check each profile shows the right services and availability.
  • Blackout dates. Confirm that closed days and vacations cannot be booked. Our guide to setting up blackout dates for salons covers the setup.
  • Payment. Pay a deposit or a full amount in test mode, then run a refund.
  • Memberships. Sign up, then pause. Our notes on freezing salon memberships show how to handle billing disputes.
  • Links from outside. Tapping a booking link in a text or an Instagram bio should open the right screen. See our walkthrough of deep links that open booking in your app.
  • Poor connection. Switch to airplane mode mid-booking and confirm the app fails gracefully.
  • Account deletion. Create an account, delete it, and confirm it is gone.

Why submissions get rejected, and how to avoid it

Problem Why it triggers a rejection Fix
Reviewer cannot log in Missing or expired demo credentials Create a permanent demo account and add notes
Crash on launch or during booking Fails the stability expectation Test on several devices before submitting
Screenshots show things the app does not do Inaccurate screenshots Capture them from the release build
Support or privacy link is dead Incomplete review information Check every URL the day you submit
App feels like a website Limited web-wrapper experience Use native screens and features such as push notifications
No account deletion Account requirements Add a delete option in settings
Privacy answers do not match behavior Disclosure rules in both stores Audit every SDK and processor, then update the forms

All of these map to points in Apple’s review guidance and Google’s Play Console requirements. A rejection is not a ban. Reply in Resolution Center, fix the specific item and resubmit.

Our perspective: own the whole brand experience

We build for barbers and beauty professionals, and the pattern we see is consistent. The salons that struggle with stores are the ones who treat the app as a separate project from the website, the booking system and the payments. Reviewers then see a thin shell, and clients see three different logos.

We think the better approach is one branded platform: the website, the app, the booking flow and the payments all carry your identity, and each barber or stylist can still control their own services, pricing and availability. Central brand rules, individual provider control. That combination is what makes an app feel complete to a reviewer and worth keeping to a client. A generic booking profile with someone else’s branding on top does neither.

The store guidelines are not an obstacle to fight. They describe, almost word for word, what a good salon app should be: stable, finished, honest about data and useful beyond a web page.

— Service

Getting a branded app without building it yourself

If you would rather not manage developer builds, signing certificates and store forms alone, look at what we offer. Our Website + Booking + Apps plan is $299 per month and includes your own branded iOS and Android apps, along with the website and booking system. The Website + Booking plan is $199 per month, and a Business Website is $49 per month. Each additional location is $49 per month. See the full pricing page for what each plan includes.

Getexclusively

You can look at branded mobile apps for barbershops to see the screens clients get, or book a call and ask how publishing to the stores works for your business before you commit.

FAQ

How much does it cost to publish a salon app?

Apple’s developer program is US$99 per membership year, or the local-currency equivalent where available. Check Google’s Play Console page for its current registration fee. Design, development or software subscription costs come on top of the store accounts.

How long does app review take?

Review times vary, and neither store promises a fixed turnaround. The reliable way to shorten it is to avoid avoidable rejections: complete metadata, working links and demo credentials. For Google Play, add the closed testing period if your personal account is new.

Do I need a separate app for each barber in my shop?

Not necessarily. One branded app can list several providers, each with their own services, prices and availability. That keeps one store listing, one set of reviews and one icon on the client’s phone. Separate apps make sense only if you run genuinely separate brands.

Can I submit an app that is just my website?

It is risky on Apple’s side. Apple flags limited web-wrapper experiences among its common review problems. Give clients native features that justify an install, such as appointment history, push reminders and saved payment methods.

What happens if my app is rejected?

Apple tells you which guideline you missed, and you can respond and resubmit. Fix the exact issue, update your reviewer notes and resubmit. Most rejections for salon apps come from login access, crashes or incomplete information, all of which you can check before submitting.

Sources