The dispatch app was ready on a Friday. Drivers had tested it for two weeks, the manager signed off, and launch was set for Monday. Monday came and nothing launched: the Apple account was still waiting on company verification, Google wanted a URL for account deletion that nobody had built, and the team realized the app didn't need to be in a public store in the first place.
In custom mobile app development, writing the code is only part of the job. The other part rarely shows up in the quote: everything between "the app works" and "the app is on the phone of the person who needs it." Developer accounts, store reviews, privacy policies, mandatory updates and, for internal apps, deciding whether to publish at all or distribute privately. This article walks that path from an MVP to the App Store and Google Play.
If you're still deciding between native, cross-platform or web, start with which type of mobile app fits your company. Here we assume that decision is made.
From MVP to a first publishable version
A mobile MVP is there to help you learn fast, and that changes how you should distribute it. In the first weeks you don't need the public store. You need 10 or 20 real users to install the app and use it at work. That's what TestFlight on iOS and Google Play's internal and closed testing tracks are for. (We covered how to scope that first version in what to include in an MVP.)
At Disrupsoft we build with Flutter, which produces the iOS and Android versions from a single codebase. That saves development work, but it doesn't save you the paperwork: each store has its own accounts, rules and timelines, and you have to go through both processes separately.
The practical move is to open the developer accounts on the day the project starts. It's the step that slips most often, and it doesn't depend on the technical team.
Developer accounts: in the company's name, and early
The account should belong to your company, not to the vendor or an individual developer. If the vendor publishes under its own account, the store considers the app theirs, and transferring it later is a chore nobody wants.
| Apple Developer Program | Google Play Console | |
|---|---|---|
| Cost | USD 99 per membership year | USD 25, one-time fee |
| Company identification | D-U-N-S Number, enrolled by someone with legal signing authority | Organization account (company identity verification) |
| Testing before launch | TestFlight | Internal, closed and open testing tracks |
| Private distribution | Custom apps through Apple Business | Private apps in managed Google Play |
Apple requires organizations to have a D-U-N-S Number (government entities excepted), and the person enrolling must have legal authority to bind the company. If your company doesn't have one yet, request it first, because it can take several days.
On Google, open an organization account rather than a personal one. Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before they can apply for production access. That rule is scoped to personal accounts, which is one more reason to register as a company.
What the stores check before approving
The stores don't just check that the app opens. They also look at how it handles people's data, and in our experience that's where first submissions get stuck most. Before you submit, have this ready:
- A privacy policy published at a URL, stating what data the app collects and why. In Chile, Law 21.719 on personal data protection will also require what you declare to match what the system actually does.
- Each store's data declaration: App Privacy details in App Store Connect and the Data safety section in Play Console. It has to match what the app and its libraries do, analytics SDKs included.
- Account deletion. If the app lets people create accounts, Apple requires that they can initiate account deletion from within the app. Google asks for the same in-app path plus a web link where users can request deletion of their account and data.
- A test login with sample data if the app requires sign-in. Without it, the reviewer can't get in and rejects the build.
- Screenshots, description and icon in the formats each store asks for.
One thing about internal apps: if the app only works for employees signing in with a company account, ask yourself whether it belongs in a public store at all. Often it doesn't, and that's what the private channels below are for.
Updates: publishing isn't the finish line
A published app has to keep up even if you add no features. Google Play sets a minimum Android API level for new apps and updates. Under the current policy, since August 31, 2026 new apps and updates must target Android 16 (API 36) or higher, and existing apps that don't reach Android 15 (API 35) stop being available to new users on newer Android versions. That floor goes up every year.
Apple also raises the minimum Xcode and SDK versions required to submit apps from time to time. If nobody rebuilds and tests the app for a year, the next urgent fix may first require updating dependencies.
So when you hire the development, ask who takes care of these updates after delivery.
Internal apps: private distribution
Plenty of custom apps have no reason to be in a public store: the field technicians' app, the warehouse inventory app, the internal approvals app. Private channels exist for these.
On iOS, Apple offers custom apps: the app goes through App Store review, but only the organizations you specify can see it, in their Apple Business account, and they distribute it through mobile device management (MDM) or redemption codes. There's also the Apple Developer Enterprise Program (USD 299 a year), but Apple reserves it for use cases not adequately addressed by the App Store, custom apps, Ad Hoc distribution or TestFlight, and requires a verification interview. For most companies, custom apps are enough.
On Android, managed Google Play lets you publish private apps visible only to your organization's users, usually through the device management console.
If you plan to hand out the installer outside any store, check Android developer verification: it took effect on September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, and Google says it will expand globally in 2027 to all apps on certified Android devices. If you publish through Google Play, registration is automatic.
Checklist before you submit
- Apple and Google accounts in the company's name, with D-U-N-S and verification complete.
- Channel decided: public store, private distribution, or both.
- Privacy policy published and each store's data declarations filled in.
- In-app account deletion (plus a web link for Google), if the app creates accounts.
- A test login for reviewers.
- Testing with real users on TestFlight and a Google Play closed track.
- An owner and a budget for the yearly SDK and API level updates.
Frequently asked questions
How long does app approval take?
It depends on the store and the app, and timelines change. What usually takes longest is the groundwork: verifying the company, getting the D-U-N-S Number, or fixing a privacy rejection. Leave slack in the calendar instead of setting launch for the day after submission.
Can I publish the app under the vendor's account?
You can, but we don't recommend it. The app is tied to the account that publishes it. The sound setup is for your company to own the account and give the vendor user access.
Does an internal app have to go through Apple's review?
If you use custom apps, yes: they go through App Store review even though only your organization can see them. The Enterprise program is another route, but Apple limits it to specific cases, requires a verification interview and evaluates members on an ongoing basis.
Getting your app to the store
At Disrupsoft we build custom mobile apps with Flutter for iOS and Android, and we work with you from the initial idea to delivery. If you have an MVP running or an app that needs to reach production, let's talk about your project.



