Getting a coaching app onto the Play Store and App Store

To get a coaching app onto the Play Store and App Store, open developer accounts in your institute's name and submit a build that reviewers can use. Both stores need a D-U-N-S number for an organisation account, plus accurate listings and privacy declarations. Most rejections are avoidable: no working demo login, no account deletion, privacy answers that don't match the app, or payments that break store rules. Names or logos that suggest a link with an exam body or the government cause trouble too.

Whose account the app should sit in

The developer account that publishes an app controls its listing, its ratings and reviews, and every update. The app's identity on each store, its package name on Android and bundle ID on iOS, can't be changed later. So the account matters more than any feature.

For a branded app, that account should be your institute's. Apple's App Store Review Guideline 4.2.6 goes further. Apps made from a commercial template or app-building service are rejected unless the provider of the app's content submits them directly. Such services shouldn't submit apps for their clients. In practice, your vendor builds the app and you publish it from your account.

You don't need to share passwords to make this work. Both stores let the account holder invite other people with limited roles, so your vendor can upload builds and manage listings without owning anything. Our guides to making an app for coaching classes and white-label LMS for coaching institutes explain the ownership choices.

Setting up the two developer accounts

Sources: Google Play's account requirements and Apple's enrolment page. Apple doesn't accept trade names or branches, and says that name mismatches delay approval. Use your legal name exactly as it appears on your registration and your D-U-N-S record.

For many Indian institutes, the seller line is the surprise. If the institute is a sole proprietorship, the app can carry the institute's name, but Apple will show the owner's personal name as the seller. Institutes registered as a company or LLP can enrol as organisations and show the company's name instead.

What both stores check before approving

Apple says that over 40% of unresolved issues relate to guideline 2.1, App Completeness, which covers crashes, placeholder content and incomplete information. Most of the list below is about completeness:

• A finished app. No crashes, no placeholder text, no broken links, and a working support link and privacy policy link.
  
  
• Access for reviewers. If parts of the app need a login, give reviewers a valid demo account, and keep your servers running during review. Apple allows a built-in demo mode instead only with its prior approval.
  
  
• Privacy declarations. Google's Data safety section and Apple's App Privacy details must match what the app and every library inside it collect, including analytics, crash reporting and notifications.
  
  
• Account deletion. If students can create an account, Apple requires a way to delete it inside the app. Google requires an in-app path and a web page where users can ask for deletion, even after uninstalling.
  
  
• Age ratings. Both stores ask you to complete a questionnaire about the app's content.
  
  
• A recent Android target. From 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36) or higher.
  
  
• Accurate listings. Screenshots and descriptions must show what the app really does.
  
  

Your privacy policy also has to be true under Indian law, not just acceptable to the stores. Our DPDP Act compliance checklist covers what it should say.

Common reasons coaching apps get rejected

These are general patterns, not a guarantee of how any one review will go:

1. Reviewers can't log in. Many coaching apps log in only by OTP to an Indian mobile number, which a reviewer can't receive. Provide a demo account that works without receiving an SMS, enrolled in a demo batch with real lectures, notes and a test.
   
   
2. The app looks like a website in a wrapper. Apple's guideline 4.2 expects an app to offer more than a repackaged website. Native video playback, tests, downloads and notifications help.
   
   
3. Payments break the store rules. Apple's App Review Guidelines (section 3.1) and Google Play's payments policy set out when a store's own billing must be used for digital content and classes. The rules are detailed and change from time to time. Agree your payment set-up with your provider before you submit.
   
   
4. Privacy and deletion gaps. A missing deletion option, or a Data safety answer that contradicts what the app sends, is a frequent and easily fixed cause.
   
   
5. Misleading names, logos or claims. Google Play's impersonation policy gives the example of an app using a national emblem to suggest government affiliation. It also doesn't allow "Official" in a title without the necessary rights. Apps that share government information, such as exam notices, must name their sources and make clear they don't represent a government body. Describing the exam you prepare students for is different from implying a link with the body that conducts it.
   
   
6. Template apps from the wrong account. An app submitted from a vendor's account under guideline 4.2.6, or several near-identical apps, can be rejected.
   
   
7. Thin or placeholder content. Empty courses, sample text or a test screen with no tests make an app look unfinished.
   
   
8. Content you don't have rights to. Scanned textbooks, another institute's material or music in a promotional video can trigger an intellectual property complaint or rejection.
   
   

Review times, and what to do after a rejection

Apple says it typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours, as its App Review page explains. Google doesn't give a fixed time, and says reviews for some developer accounts can take up to seven days, or longer in exceptional cases.

If an app is rejected, the notice names the guideline or policy involved. Read that section, fix the cause rather than the symptom, and say what you changed when you reply or resubmit. If you believe the decision is wrong, both stores let you respond or appeal. Resubmitting an unchanged build rarely helps and can slow things down.

Keep a short internal log of each rejection and the fix. The same issues tend to come back with each new feature, and a log saves the next person days.

Keeping the apps live after launch

Approval is the start, not the end. To keep the apps available:

• Update every year. Google raises its target Android version requirement each year, and Apple updates its own requirements for new submissions. Agree with your vendor who does this work.
  
  
• Renew Apple's membership. It is yearly. If it lapses, your apps are no longer available on the App Store.
  
  
• Keep contact details working. Policy warnings go to the account's contacts, and Google requires its verified contact details to stay operational.
  
  
• Watch policy emails. Stores give deadlines for changes. Missing one can mean an update is blocked or the app is removed.
  
  
• Watch for fake apps. Search the stores for your institute's name now and then, and report impersonation through each store's forms.
  
  

For the wider build-or-buy decision, see how to create your own coaching app.

Upclass gives coaching institutes branded apps in their own name on Android, iOS, Windows and Mac, with courses, live classes, tests and online test series. Student fees go to the institute's own payment gateway. VidSafe protects the lectures with VidSafe proprietary encryption, dynamic watermarking, screen- and camera-recording detection, account-sharing prevention and RASP. See the full platform on our LMS for coaching institutes page.

Frequently asked questions

How long does it take to get an app approved on the Play Store?

Google doesn't promise a fixed time. It says reviews for some developer accounts can take up to seven days, or longer in exceptional cases. New personal accounts must also run a closed test with at least 12 testers for 14 days first. Allow time for verification and testing as well as review.

Do I need a registered company to publish on the App Store?

Not to publish, but it decides whose name appears as the seller. Apple enrols only legal entities with a D-U-N-S number as organisations, and doesn't accept trade names. A sole proprietor enrols as an individual, and the owner's personal legal name is shown as the seller.

What is a D-U-N-S number, and is it free?

A D-U-N-S number is a nine-digit business identifier issued by Dun & Bradstreet, which Google and Apple use to verify organisations. Google says applying is free and can take up to 30 days, and warns about third-party services that charge for it. Make sure the name and address match your legal registration.

Can my app vendor publish the app from its own account?

It can on some stores, but it isn't a good idea. The account holder controls the listing, reviews and updates, and Apple's guideline 4.2.6 expects template-based apps to be submitted by the content provider. Publish from your own accounts and give the vendor a limited role instead.