Your Accounts
Tepia submits under developer accounts your company owns, enrolled as an organization, so the listing never depends on an agency login.
Read: App Store and Google Play Rejection Fixes
To launch an app on the App Store and Google Play, enroll your company in both developer programs, prepare listings and privacy disclosures, beta test through TestFlight and a Google Play testing track, submit for review with a working demo account, and release in stages. Tepia handles submissions under accounts your company owns and reserves about a month for launch, including review and staged rollout.
Most launch delays come from accounts, privacy disclosures and review notes, not from the code.
Tepia submits under developer accounts your company owns, enrolled as an organization, so the listing never depends on an agency login.
Read: App Store and Google Play Rejection FixesTepia supplies a demo account, review notes and sample data, so an app behind a login is never rejected because a reviewer got stuck.
Read: How to Develop an App From Idea to Launch (12 Steps)Apple's privacy details and Google's Data safety form are completed from an audit of every SDK in the build, not from memory.
Read: Mobile App Release Management and Continuous DeliveryReleases use Apple's phased release and Google's staged rollout, so a crash reaches a small share of users before it can spread.
Store figures Tepia plans around when launching mobile apps.
Apple states that App Review typically reviews 90 percent of submissions in less than 48 hours and at least half within 24 hours.
Apple's 2024 App Store Transparency Report shows 1.9 million of 7.8 million submissions were rejected, about 1 in 4.
Pew Research Center reports about 90 percent of US adults own a smartphone, so most of your audience can install on launch day.
Launching starts weeks before the build is ready. Enroll your company in the Apple Developer Program as an organization, which requires a DUNS number and a verified legal entity, and create a Google Play developer account in the organization’s name. Verification on either side can take days or weeks, so Tepia asks clients to start during development rather than in launch week.
Organization accounts matter for more than speed. Your company appears as the seller on the listing, team members can be invited with specific roles, and the app never depends on one person’s login. Google also applies stricter testing rules to newer personal accounts, including a closed test before production access. Tepia publishes every client app under accounts the client owns, which also makes any future change of vendor painless.
Tepia keeps a launch checklist for every client app and pushes a beta build through the same steps early, so account or listing problems surface well before the real launch date.
Most rejections are predictable. Tepia checks each of these before every first submission.
| Issue | Store | How to prevent it |
|---|---|---|
| Crashes or broken links during review | Both | Test the exact build on physical devices and check every link in the listing |
| Reviewer cannot log in | Both | Provide a demo account with data and explain any two factor step |
| App is a thin website wrapper | Apple | Add native value such as offline access, push notifications or device features |
| Account creation without in app deletion | Apple | Let users delete their account from inside the app |
| Third party login without a private option | Apple | Offer Sign in with Apple or another login that meets Apple’s privacy rules |
| Digital goods sold outside in app purchase | Apple | Use in app purchase for digital content and subscriptions where the rules require it |
| Data safety form does not match SDK behavior | Audit analytics and advertising SDKs before filling in the form | |
| Vague permission requests | Both | Explain camera, location or contacts use in plain words in the prompt |
If you are already stuck in a rejection loop, see App Store and Google Play rejection fixes.
Approval is not the finish line. Apple’s phased release spreads an update to users with automatic updates over seven days, and Google Play’s staged rollout lets you choose the percentage of users who receive it; both can be paused if crash rates climb. Tepia releases first launches and major updates this way by default.
Watch these closely in the first two weeks:
Plan the first update before launch. A small release two to three weeks later fixes what real users find and shows customers the app is maintained. Tepia’s release management practice sets up the CI pipeline so updates ship on a steady rhythm.
Launch preparation runs through all six of Tepia’s phases, not just the last one.
On a full build, Discovery typically takes 1 to 3 months and development and QA 2 to 6 months, and Tepia reserves about a month for launch itself. See our process, the full guide to developing an app, or ask Tepia to review your launch plan.
A paragraph or two with information on your product/service or describes a problem your product/service is designed to solve.
CEO
Senior Project Manager
VP & Operations Manager