Publishing an app is a different job than building one. Here are five things I wish someone had told me before I submitted SkyCast Pro for review.
1. Closed Testing Checks Real Usage, Not Just Headcount
Google's 12-tester, 14-day closed testing requirement isn't just a box to tick. If your testers install the app and never open it again, Google can (and will) reject your production application for insufficient genuine engagement. The fix is simple but easy to overlook: actively remind your testers to open the app regularly during the full testing window, not just install it once.
2. Your Privacy Policy and Data Safety Form Have to Match Reality
It's tempting to fill out the Play Console's Data Safety questionnaire quickly and move on, but the answers have to accurately reflect what your app and its SDKs (ad networks especially) actually collect. AdMob, for example, collects more than most developers initially realize — device identifiers, approximate location, and diagnostic data — all of which need to be disclosed even if you didn't write the code that collects it.
3. Test-Mode Ads Are a Feature, Not a Bug — Until Launch Day
Testing your own ads in production mode is against AdMob policy and can get your account suspended. Keep test ads on throughout closed testing, and only flip to live ad units right before (or immediately after) your production release goes live. It's a small toggle with a big consequence if you forget it either direction.
4. A Low Network Timeout Will Look Like a Bug to Your Users
An overly aggressive network timeout (say, 3-4 seconds) can make a perfectly working app look broken on a slow connection — showing "offline" or stale cached data even though the user has a signal. If you're going to err, err toward a longer timeout with a clear loading state, rather than failing fast and showing a misleading error.
5. Reviews Are Your Best (and Sometimes Only) QA Signal
Once your app is live, user reviews will catch things your own testing never will — specific devices, specific regions, specific network conditions you didn't think to test. A single 1-star review that says "doesn't search for location" is worth treating as a real bug report, not just noise to brush off. Reply to it, fix it, and ship the fix quickly; it tells future users you're actually maintaining the app.
Publishing SkyCast Pro taught me that the app review process and the post-launch feedback loop are part of the engineering work, not a formality tacked onto the end of it.