One update, both stores, no rewriting
Shipping a mobile update means writing release notes twice — once for the App Store and once for Google Play, each with different length limits and conventions. This builder takes a single set of features and fixes and produces a properly formatted note for each store, with live character counts so you never get rejected for overflowing the field.
How it works
You enter the app name, version, and tone, write a short What’s New headline, and list new features and bug fixes one per line. The builder constructs two outputs from the same input. The iOS version uses a tone-matched intro, bullet-pointed features, a separate bug-fixes section, and a polite rating nudge, fitting the App Store’s generous 4000-character field. The Android version is compact and plain — leading with the version number — to fit Google Play’s 500-character limit, and the tool warns you when you exceed it. Each store gets a copy button so you paste the right text into the right console.
Tips and example
- Lead with the single change users care about most, for example
Faster exports and a fresh dark mode, not a laundry list. - Keep Google Play notes tight; if the counter goes red, cut the least important fix line.
- Match tone to category —
professionalfor a banking app,playfulfor a game. - Reuse the same notes as your in-app “What’s New” screen so messaging stays consistent.