Google Play developer account
US$25 one-time
Identity verification with a government ID and a payment card under your legal name.
Source: Google Play Console Help: register for a developer accountApp Store Publishing · Both stores · Accounts in your name
Get your app into the App Store and Google Play
Publishing is not one upload button. Each store has its own account verification, fees, signing keys, testing requirements, privacy declarations and review process, and the rules change every year. We run that process for you, in accounts registered to your company, so you own the listings and nothing stalls your launch.
Still need the app built first? That is a separate service. Mobile app development →
Who this is for: Founders and businesses with a finished or nearly finished app, and teams whose previous developer never completed the store release.
What the stores require
The rules that decide whether your launch date holds.
Checked against the stores' own documentation. Each card links to its source.
Google Play, personal accounts
12 testers · 14 days
Accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 consecutive days before they can apply for production access. Google says the application review usually takes seven days or less.
Source: Google Play Console Help: app testing requirementsGoogle Play, organisation accounts
D-U-N-S number required
An organisation account cannot be created without one. Google notes obtaining it can take up to 30 days, so it is the first thing we start.
Source: Google Play Console Help: D-U-N-S numbersApple Developer Program
US$99 per year
Organisations need a D-U-N-S number, must be a legal entity (no trade names), and the person enrolling must have authority to sign for the company. Prices vary by region.
Source: Apple Developer Program enrollmentApple App Review
No published turnaround
Apple does not commit to a review time. We never schedule a public launch on the day of submission, and we answer reviewer questions the same working day.
Both stores, every release
Privacy and data declarations
A public privacy policy, accurate data-collection declarations, working account deletion where there is sign-up, and permissions the app can justify. Mismatches are the most common reason for rejection we see.
What you would get
The parts, in plain words.
Each part has a plain name and, underneath, what engineers call it. You never need the second one to talk to us.
Store accounts in your company's nameApple Developer Program · Google Play Console
Registered to you, with our team added as developers you can remove at any time.
The keys that prove the app is yoursKeystore · certificates · provisioning profiles
Created, documented and handed to you. Without them nobody can publish updates.
A private test with real peopleTestFlight · Google Play closed testing
Both stores check that real people have used the app before it goes public.
Listings that pass reviewStore listings · data safety · privacy labels
Screenshots, descriptions and the privacy declarations that must match what the app does.
Someone handling the reviewersApp Review · Play Console correspondence
We answer questions, fix what is flagged and resubmit until it is live.
How it works
How it works, step by step.
- 01
Accounts registered to your company
We set up or audit the Apple Developer Program and Google Play Console accounts in your company's name and add our team as developers. You hold the ownership and the payment method.
You provide
Company legal details, D-U-N-S number (we guide the application), a payment card, a support email address.
We do
Enrolment steps, verification follow-ups, team roles and permissions.
- 02
Readiness review
Before anything is uploaded we check the app against the current store rules: permissions, sign-in and account deletion flows, privacy policy wording, data declarations, target platform versions, and listing assets.
You provide
Access to the codebase, the privacy policy page (or we tell you exactly what it must say), icon and brand assets.
We do
A written checklist of fixes with the rule each one maps to.
- 03
Signing and release builds
Keystores, Apple distribution certificates and provisioning profiles are created, documented and stored in your possession. Release builds are produced from a repeatable pipeline, not from one person's laptop.
We do
Key generation, secure storage guidance, build configuration, versioning.
- 04
Testing tracks
TestFlight on iOS and internal or closed testing on Google Play. If your Google Play account is a personal account, we plan the 12-tester, 14-day closed test into the schedule from day one.
You provide
Real testers who will install and use the app. The stores check this; it cannot be faked.
We do
Tester onboarding instructions, build distribution, feedback triage.
- 05
Listings, submission and review
Store listings, screenshots, data safety and privacy labels, content ratings and pricing are completed and submitted. We respond to reviewer questions, fix what is flagged and resubmit until the app is live.
We do
All submission work and reviewer correspondence, with you copied on every exchange.
- 06
After launch
Staged rollouts, crash monitoring, and updates when Apple and Google raise their platform or policy requirements. This is where most apps that were published once quietly fall out of the stores.
We do
Ongoing maintenance under a separate agreement if you want it.
What affects the price
The questions that move the price up or down.
We price on scope, not guesswork. If you can answer these, we can give you a number quickly. If you cannot yet, we work them out together on the first call.
- 01Is your store account a personal account or a company account? Personal Google Play accounts need the 12-tester closed test.
- 02Is the app finished, or does it need fixes before it can pass review?
- 03Do you already have a privacy policy and the signing keys, or do they need to be created or recovered?
- 04One store or both?
Packages
Packages that usually fit this goal
Starting prices for a written scope. The exact price follows the plan you approve.
You own the code. Everything we make for you is yours as soon as each stage is paid for, and you can see the code from the first day.
Prices for
- Keep it running
Ongoing Maintenance
₹5,000 – ₹10,000 per month in India$250 – $750 per month outside India
Monthly care for a live app: updates, fixes, monitoring, and a response time written into the agreement.
All packages, what each includes, and what is always extra →
Where it goes wrong
Launches stall on things nobody warned you about: a Google Play personal account that cannot publish until twelve testers have used the app for fourteen days, an organisation account waiting on a D-U-N-S number, a rejected build because the privacy declarations do not match what the app actually does, or signing keys that were never handed over by a previous developer.
What you end up with
Live, searchable listings on both stores, registered to your company, with signing keys and credentials documented and in your possession, and a maintenance plan for the OS and policy updates that follow.
What you need
Bring these and we can start.
- A finished or nearly finished app (we can also review an unfinished one)
- Company legal details and a D-U-N-S number for organisation accounts
- A payment card for the store fees, held by you
- A public privacy policy URL
- App icon, name and brand assets
- Real testers for a Google Play closed test if your account is personal
What you get
What is included.
- Apple Developer Program and Google Play Console accounts in your company's name, with our team added as developers
- Signing keys, certificates and provisioning profiles created, documented and handed to you
- Completed store listings, screenshots, data safety and privacy declarations
- Submission, reviewer correspondence and resubmission until the app is live
What happens after you contact us
No sales calls. Here is the actual sequence.
- 01
An engineer reads your message and replies within one business day with the first things we would check.
- 02
A short call to look at the app, the accounts you have, and anything a previous developer left behind.
- 03
A written plan: the steps, what you provide, what we do, and a price.
- 04
Work starts when you approve it. You are copied on every exchange with Apple and Google.
Technical detailsfor your technical advisor
Release engineering for Flutter and native apps on both stores.
- Upload keys and app-signing keys are separated; Play App Signing is enabled so a lost upload key can be reset.
- Build numbers, version names and release notes are managed from the repository, not by hand.
- Data safety and privacy nutrition labels are derived from an inventory of SDKs and permissions in the app.
Stack
- Flutter
- Android (Kotlin)
- iOS (Swift)
- Play App Signing
- TestFlight
- Fastlane-style scripted builds
Questions we get asked
Frequently asked questions
How long does store review take?
Google says its review of a production-access application usually takes seven days or less, and app reviews are typically quicker. Apple does not publish a turnaround time. We plan launches with a buffer of at least a week after submission and never promise a date the stores have not confirmed.
Do you publish under your own developer accounts?
No. The accounts, listings, keys and customer relationships belong to you, so they are registered to your company. We work inside them with developer access that you can revoke at any time.
Our previous developer disappeared with the keys. Can you still publish?
Usually yes. If the original signing key is lost, Google Play supports key upgrades for apps enrolled in Play App Signing, and on iOS certificates can be reissued from your Apple account. We assess what exists before quoting.
Why do we need twelve testers?
Google requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers opted in for 14 consecutive days before production access. Organisation accounts are not subject to this rule, which is one reason we recommend an organisation account for businesses.
What happens if the app is rejected?
We read the reviewer's notes, map them to the specific guideline, fix the app or the declarations, document the change and resubmit. Rejections are common on first submission and are part of the work, not an extra.
Next step
Tell us where you are today.
An idea, a spreadsheet that hurts, an app that is stuck: describe it in your own words and an engineer will reply within one business day.
- No charge for the first conversation
- NDA on request before you share code
- Accounts, keys and listings stay yours