Submitting an app to the App Store and Google Play
Store submission requires more than uploading a working build. Account ownership, accurate listing materials and privacy disclosures all belong in the release plan. Preparation can start during development, while approval and its timing remain decisions made by the platform.
Updated: · tealtap

Choose the right account and keep ownership clear
Decide which person or organisation will publish the product before registration begins. Record who can accept agreements, administer access and recover the account. A company product needs an ownership arrangement that survives staff changes. Give collaborators appropriate roles rather than relying on a shared owner password.
Apple organisation enrolment can involve verifying the legal entity and the authority of the person enrolling, including relevant D-U-N-S information. Google also distinguishes personal and organisation accounts and requires identity information appropriate to the account. Check the current official process early, rather than discovering missing business records when the finished application is ready to ship.
Treat signing access and recovery as part of handover. The product must remain releasable when a supplier or employee changes. Keep an inventory of responsible people and permissions, while keeping credentials and private keys out of public documents and initial enquiry messages.
Official registration fees are separate from project work
The published Apple Developer Program fee is 99 USD per year, with local currency pricing where available and regional differences possible. Google publishes a one-time Play Console registration fee of 25 USD. These are platform charges, not tealtap development prices. Verify the official pages and the price shown during registration before paying.
Account registration does not cover the work of preparing screenshots, testing a release, resolving review feedback or maintaining later versions. Selling digital products can also involve additional commercial conditions that need assessment for the actual business model. Do not infer the total release effort from the registration fee. Agree who pays the platform directly and who keeps membership and billing information current.
Prepare materials that match the submitted product
The app name, description and screenshots should represent the functionality in the submitted release. Localised materials must describe the same product behaviour. Assign owners for content, support details and the answers needed for content classification. These tasks are not always development work, but missing decisions can prevent a technically finished application from being submitted.
Where a main workflow requires login or special equipment, prepare a practical way to assess it. Review access should use suitable test data and remain available while the submission is being evaluated. Check the connected service and the instructions together. A working build is difficult to review if the account has expired or the described journey cannot be reached.
Base privacy disclosures on actual data flows
Apple App Privacy and Google Data safety disclosures need to reflect the application’s behaviour, including relevant third-party SDK activity. Make an inventory of data leaving the device, its purpose and the services involved. Technical and data responsibility should meet here: neither a developer guessing the business purpose nor an owner guessing SDK behaviour is a reliable process.
Check the disclosures against the interface and privacy notice. Revisit them when analytics, diagnostics or another component changes. Store labels do not replace the work of establishing appropriate legal grounds and user processes. Keep the assessment connected to the release so later maintainers can see which components and behaviours were considered.
Plan verification, testing and review separately
Account verification, testing, approval of listing materials and platform review are different stages. Google’s publishing guidance notes that some submissions can need longer review. Allow for corrections and resubmission rather than promising that a particular launch date follows automatically from uploading the build.
New personal Google Play accounts can have specific testing and production access requirements. Check the current official guidance when planning the account. Organising testers and preparing evidence of readiness can require work before public distribution becomes available. A release plan should cover eligibility to publish as well as the technical upload.
Agree how the public launch is authorised after approval. Someone should check the listing, installation and first login in the released version. Marketing, support and operations should use the same confirmed status. If one platform becomes available earlier, decide whether separate launches are acceptable and how users will be informed.
Respond to review feedback with evidence
Apple’s review guidance makes app completeness and accurate presentation relevant checks. A broken login, unfinished content or a mismatch between the listing and the product can create a problem. Minimum functionality requirements can also matter for an application that primarily wraps web content. Read any feedback against the cited requirement and the submitted version.
Preserve the platform message, reproduce the reported situation and separate a product defect from information that needs clarification. If behaviour changes, recheck the description and test instructions too. A resubmission response should identify the specific correction and how it can be checked, rather than making a general promise about a future release.
Keep the product releasable after approval
After publication, check the actual release and the core connected workflow. Support details should work and someone should own incoming reports. Future versions can require updated materials, testing and review even when the business workflow changes little. Compatibility and dependency maintenance remain part of running the product.
Keep the release identifier, build instructions and verification record for handover. Source code, store access and connected service access together determine whether another team can maintain the product. Close the release against the agreed handover conditions, then keep account and operating responsibilities current.
Frequently asked questions
What are the official account fees?
Apple publishes an annual 99 USD programme fee, with regional pricing possible; Google publishes a one-time 25 USD registration fee. Verify the official sources before payment.
Can review timing be guaranteed?
No. Account checks, testing requirements, review and corrections can all affect public availability.
Who should prepare privacy disclosures?
The people responsible for technical data flows and data handling should prepare them together against the application’s actual behaviour.
Discuss your project
Describe the current application, intended stores, existing developer accounts and unresolved release questions. Redacted screenshots and test examples are enough for an initial discussion; do not send passwords or signing keys.


