How do you publish a Flutter app to Apple and Google?

Flutter produces separate iOS and Android releases from a shared project, but each store has its own accounts, signing, policies and review process. Submission should be planned during development rather than treated as an upload at the end.

Set up business-owned accounts

The client should normally own its Apple Developer and Google Play accounts. Organisation verification can take time and may require registered-company details. Supplier access can then be granted without transferring ownership later.

Manage signing securely

Certificates, keys and provisioning connect a release to its publisher. Store them through a controlled process with recoverable access. Losing credentials or leaving them on one developer’s computer creates avoidable operational risk.

Prepare accurate store information

Names, descriptions, categories, screenshots, support links and privacy information should reflect the real app. Screenshots need current devices and interfaces. Claims and subscription terms must be clear.

Complete privacy declarations honestly

Apple and Google ask what data is collected, why and whether it is linked to a person. Review analytics, advertising and third-party packages as well as information entered directly by users. Store declarations and the public privacy policy must match the implementation.

Use staged testing and release

TestFlight and Play testing tracks allow invited users to try signed builds. Staged rollout can limit the first public audience while crashes and feedback are monitored. A rollback plan should account for backend compatibility with older versions.

Allow for review questions

Provide working test accounts and clear notes for restricted features. Review timing varies and rejection may require changes or explanation. A fixed marketing launch should include contingency rather than assuming same-day approval.

Store preparation, submission and release monitoring are included in our Flutter app development service.