Releases · 03 / 05
Versions & release tracking
iOS and Android run independent review processes. Manage them as the separate workflows they are, while keeping a unified view of both pipelines.
Create a version per store, write its release notes, attach a build, and submit it for review. Each store maintains its own timeline of in-review, live, archived, and rolled-back versions, so each platform ships at the pace it allows without forcing them in lockstep.
- Separate iOS and Android workflows, side-by-side
- Write release notes and attach a build in one screen
- Submit to App Store Connect or Play Console in one click
- Track in review, live, rolled back, and archived states
Inside the feature
What you get
Separate iOS and Android timelines
Each store maintains its own version history. Submit when a store is ready, independent of the other. App Store review delays no longer block your Play release.
Release notes editor
Write notes per store, per language. Reuse a template across versions or compose fresh notes per release.
Build attachment
Select which build maps to which version. Reuse a previous build for a new version if required. Every version references a known artifact.
Status at a glance
Published or draft: every version displays its current state on both stores. Filter by status, identify pending items, and jump to the relevant console in one click.
Use cases
When teams reach for this
Prepare a draft ahead of time
Draft a version, write its release notes, and attach a build days before launch. Keep it in draft until the team gives the go-ahead, then publish to both stores.
Publish per store, on each store's pace
Push iOS the moment the build is ready without waiting on Android, or vice versa. Each store has its own draft and its own published version, so neither blocks the other.
Localized release notes in one pass
Write one set of release notes, translate them per language for both stores, and publish the localized version everywhere at once.
FAQ
Anything specific?
A draft lives only in Releasely: you can edit release notes, swap the attached build, and adjust localizations freely. Once published, the version is sent to App Store Connect or Play Console and tracked as the live version on that store.
Once a version is published, its store metadata is locked. To change the release notes, you create a new version: on the App Store it goes back through App Review, and on Google Play it ships as a new release. Swapping the build works the same way, since each published version maps to a single artifact on the store.
Yes. Each store has its own version with its own draft and published state. Publish iOS today, keep the Android version in draft, and ship it whenever the build is ready.
Each version exposes one editor per language, per store. Translate once, and the localized notes are pushed to App Store Connect and Play Console with the rest of the version when you publish.