QA passed. Marketing scheduled the announcement. Then App Store Connect rejected the build for a missing privacy manifest. Play Console flagged the data safety form. TestFlight testers saw a white screen on first open because production API keys were not set.
Store submission is a gate separate from "feature complete." Flutter compiles to both stores, but Apple and Google review different artifacts, policies, and metadata. This checklist is what we run before calling a Flutter release done, distinct from deep links or state management work covered in other posts.
We ship cross-platform mobile delivery with teams who need predictable store releases, not Friday-night fire drills.
Mental model: three layers
Flutter build (release mode, correct flavor, env config)
