App store submission
Prepare Apple and Google developer accounts, store information, testing, review, and release.
Publishing a native app is a partnership between Mango9 and the app owner. Mango9 can prepare the approved mobile version and native build. The owner controls the Apple and Google accounts, verifies their identity, accepts legal and tax agreements, supplies truthful store and privacy information, tests the package, answers reviewer questions, and decides when to submit and release.
Store rules and required operating-system versions change. Use this page as the preparation path, then confirm the linked Apple and Google requirements immediately before submission.
Choose the account type first
Apple Developer
Apple's paid Developer Program currently costs USD $99 per membership year, or the local equivalent where available. Eligible nonprofits, educational institutions, and government entities may request a fee waiver. Confirm current terms during enrollment.
Individual is normally appropriate for one person, including a sole proprietor or single-person business. The person's legal name appears as the seller on the App Store. Apple does not accept a trade name or DBA as an organization by itself.
Organization is appropriate for an incorporated company, nonprofit, partnership, joint venture, or government organization that can enter contracts. Apple currently requires:
- a legal entity rather than only a DBA, trade name, branch, or informal project;
- a D-U-N-S Number;
- authority to bind the organization to legal agreements;
- a work email associated with the organization's domain;
- a public, functional website associated with the organization.
The organization's legal entity name appears as the seller. Review Apple's current membership comparison and enrollment requirements before choosing.
Google Play
Google Play developer registration currently has a one-time USD $25 fee. Confirm the amount and available account options during signup.
Personal is intended for a person such as a student, hobbyist, or independent developer who is not enrolling as an organization. Google applies personal identity and contact verification. New personal accounts are also subject to additional production-access testing described below.
Organization is intended for a business or organization. It requires organization verification and a D-U-N-S Number. Use an authorized representative and organization contact details that the organization controls.
Personal and organization accounts can use the same core Play Console functionality, but their verification information and public developer identity differ. Read Google's current account-type guidance and developer identity requirements before registering.
| Decision | Apple individual / Google personal | Apple organization / Google organization |
|---|---|---|
| Best fit | A person publishing as themselves | A legal business or organization publishing under its identity |
| Public identity | Personal developer or seller identity | Verified organization or legal entity identity |
| D-U-N-S Number | Not normally required | Required by both stores |
| Account control | The person must retain access | Use organization-controlled email, recovery, and authorized administrators |
| Important consequence | Moving ownership later adds transfer and verification work | Verification may take longer, so begin before the release is ready |
Before either submission
Prepare these items before generating the final store build:
- final app name, icon, platform identifiers, version, and build number;
- support contact and a publicly reachable support page;
- a privacy policy that describes the app and its connected providers accurately;
- store description, category, screenshots, and any promotional artwork;
- age or content-rating answers;
- test accounts and step-by-step reviewer access for protected features;
- plain-language explanations for sensitive permissions;
- production API, database, and external services that the build can reach;
- device tests covering the main workflow, sign-out, poor connectivity, and errors;
- legal, tax, banking, encryption, content-rights, and regional declarations that apply.
If reviewers cannot reach a login-protected feature, provide an active demo account and explain any unusual steps. Do not submit credentials that expire during review or require the reviewer to contact a staff member for every sign-in.
Apple App Store process
Enroll and verify the owner
Create the Apple Account with two-factor authentication, choose individual or organization enrollment, complete identity and organization checks, accept the agreements, and keep account recovery under the owner's control.
Register the app identity
Confirm the bundle ID and required capabilities before the first release. Keep signing certificates, identifiers, and provisioning access inside the owner's Apple team.
Create the App Store Connect record
Add the name, primary language, bundle ID, SKU, category, pricing, territories, support and privacy URLs, description, screenshots, age rating, and required privacy answers.
Build and test
Build the exact approved Mango9 mobile version, upload it to App Store Connect, and test the release candidate through TestFlight on supported physical devices.
Prepare review access
Select the uploaded build, answer export-compliance and content questions, add review notes, and provide working demo credentials and instructions for features behind sign-in or special hardware.
Submit and respond
Choose Add for Review, verify the submission, then choose Submit for Review. Monitor App Store Connect, answer questions, correct genuine issues, and submit a new build when a code change is required.
Release
Choose manual, automatic, or phased release as appropriate. After approval, verify the live listing, installation, sign-in, production API, purchases, notifications, and support links.
Apple requires a privacy policy URL for iOS apps and asks the owner to disclose data collection by the app and its third-party partners. Review App privacy details before answering. The full workflow is documented in Submit an app, Publishing overview, and the App Review Guidelines.
Google Play process
Register and verify the owner
Choose a personal or organization account, pay the registration fee, complete the required identity and contact verification, and keep recovery and administrator access under the owner's control.
Register the application
Confirm the permanent Android package name, app name, language, free or paid status, and required declarations. Configure Play App Signing and protect the owner's upload credentials.
Prepare the Android App Bundle
Build the exact approved Mango9 mobile version as an Android App Bundle for the store. Confirm that it meets Google's current target API level requirements; the required level and deadlines change over time.
Complete the store listing and App content
Add descriptions, icon, feature artwork, phone or tablet screenshots, category, support contact, privacy policy, ads declaration, target audience, content rating, reviewer access, sensitive-permission declarations, and the Data safety form.
Test through Play
Use internal testing first, then any required closed or open test. Install the store-delivered build on supported physical devices and test sign-in, production services, upgrades, permissions, billing, notifications, links, and failures.
Request production access when required
Personal accounts created after November 13, 2023 currently must run a closed test with at least 12 testers opted in continuously for 14 days, then answer Google's production-readiness questions. Check the current personal-account testing requirement before planning the launch date.
Submit the production release
Create the production release, review warnings and country availability, send the changes for review, and monitor the Publishing overview and inbox for required action.
Release and monitor
Use a staged rollout when risk justifies it. Verify the live listing and production workflow, watch crashes and user feedback, and halt or replace the release if evidence shows a serious problem.
Google's review preparation includes truthful app-access instructions, audience and content answers, ads declarations, privacy and security details, and special declarations for sensitive permissions. Review the current App content requirements and Store setup guidance before submission.
Review is not guaranteed
Mango9 cannot promise acceptance or a review time. Apple and Google make the review decision and may ask about functionality, privacy, permissions, payments, content rights, account deletion, or reviewer access. A rejection is normally a request to understand or correct a specific issue, not a reason to create a new developer account.
Read the message carefully, reproduce the issue on the submitted build, and answer with concrete evidence. If only metadata or instructions are wrong, correct those. If behavior must change, create and test a new mobile version and submit its new build. Keep the production backend compatible with the version already in review.
Final owner checklist
- The correct person or organization owns both developer accounts.
- Recovery methods and at least one backup administrator are current.
- Bundle ID and Android package name match the store records.
- The submitted artifacts come from the approved Mango9 mobile version.
- Privacy answers include the app, SDKs, APIs, and external providers.
- Reviewer credentials work without staff intervention.
- Store screenshots and descriptions match the submitted behavior.
- The production API and database are reachable from physical devices.
- Required personal-account testing and production access are complete.
- The owner has chosen manual, automatic, phased, or staged release deliberately.
- The team will verify the live installation and critical workflow after release.