Most app delays are not code. They are accounts, testing rules and review. We set up your D-U-N-S number and developer accounts, run the tests the stores ask for, fill in the privacy forms and see the app through review.
Six steps, done in order, with every account in your company's name so the app is always yours.
A free nine-digit company number from Dun & Bradstreet. Apple needs it to enrol an organisation, and Google Play asks for it for organisation accounts. It is issued in your company's legal name, so the details must match your registration.
Your company enrolled as an organisation, so the App Store shows your business as the seller. Apple charges US$99 a year, and the membership must stay active for the app to stay on sale.
An organisation developer account in your company's name, with a one-time US$25 registration fee. Google verifies the organisation with its D-U-N-S number.
Test builds on real phones before release: TestFlight on iPhone, and the internal, closed and open testing tracks on Google Play.
Apple's App Privacy details and Google's Data safety form say what data the app collects and why. We fill them in from how the app really works.
We submit, answer the reviewers, fix anything they flag and release, with a staged rollout on Google Play when it helps.
The two stores ask for similar things in different ways. This is what each one needs from a company.
| App Store | Google Play | |
|---|---|---|
| Account in your name | Organisation account under your company's legal name | Organisation account under your company's legal name |
| Fee | US$99 a year | One-time US$25 |
| D-U-N-S number | Needed to enrol as an organisation | Needed for organisation accounts |
| Testing | TestFlight: internal testers from your team, external testers after a beta review | Internal, closed and open testing tracks. New personal accounts need a closed test with at least 12 testers for 14 days before production |
| Privacy disclosure | App Privacy details (privacy labels) in App Store Connect | Data safety form in Play Console |
| Account deletion | Apps that let people create an account must let them delete it from inside the app | Apps with accounts must offer deletion in the app and through a web link |
| Review | New apps and updates are reviewed before release | New apps and updates are reviewed before they go live |
Google's 12-tester rule applies to new personal developer accounts. A business should normally publish from an organisation account in its own name, which is one more reason to get the D-U-N-S number early.
Physical goods and services can be paid through a gateway such as Razorpay. Digital content and subscriptions used in the app usually have to go through Apple's in-app purchase and Google Play billing.
The slow parts start first, so nothing waits on paperwork at the end.
Any business shipping an app, whether we built it or another team did.
Learning apps for students and parents.
A mobile companion for a web product.
Ordering and loyalty apps.
Class booking and membership apps.
Guest apps for stays and services.
Booking and reminder apps for patients.
Connections we set up as part of the build. See every integration.
Payments for goods and services. Digital content sold inside an app usually has to use the store's own billing.
From install to use: see what people do after they download.
A support chat link inside the app.
Sign-in, receipt and password reset emails.
A D-U-N-S number is a free nine-digit identifier that Dun & Bradstreet gives to a business. Apple uses it to confirm that your company exists as a legal entity before it enrols you as an organisation, and Google Play asks for it when you open an organisation account.
Apple charges US$99 a year for the Apple Developer Program. Google Play Console has a one-time US$25 registration fee. These fees are paid to Apple and Google from your own accounts.
Because the app is yours. The account holder controls the listing, the reviews, the payouts and the right to update the app. With the accounts in your name you can change developers at any time without losing the app.
Google asks new personal developer accounts to run a closed test with at least 12 testers who stay opted in for at least 14 days before the app can go to production. Organisation accounts are not held to that rule, but we still test on real phones before every release.
Both stores ask you to declare what data the app collects, what it is used for and whether it is shared. On Apple this is the App Privacy section in App Store Connect, shown on your App Store page. On Google Play it is the Data safety form. The answers must match how the app really behaves.
Rejections are common and usually fixable. We read the reviewer's notes, change the app or the listing, reply in the review thread and submit again.
Yes. We review the build and the code access first, then take it through accounts, testing, listings and review in the same way.
Book a call or message us on WhatsApp. Tell us where the app is today and we will list what the stores still need from you. You can also write to support@duedoor.com.
