Do I have to create a release?

No. Every version number your builds carry has a release page already. Nothing extra is stored.

Does it work without a store connection?

Yes. Builds, readiness, channels, checklist and timeline work without one. The App Store and Google Play part needs your store connection and the app shared with AppForShare.

Which plan do I need?

Team for the full page with the checklist and approvals. Pro gets the read only view.

AppForShare Create a free account

Everything about one version, on one release page

Team (Pro gets a read only view without the checklist and approvals)

On release day the answers to "where is 2.4?" sit on several pages: the iOS build, the Android build, the store readiness check, the checklist, App Review, TestFlight and the Google Play rollout. The release page puts one version together, for both platforms, with a timeline of who did what.

It keeps nothing of its own. It reads what AppForShare already has about that version, so it stays in step with the build pages, the App Store review card and the Google Play releases page.

Start free See plans

Example

Release 2.4.0, Shop app

iOS (118), Android (58)Ready, no blockers
Checklist and approvals1 approval waiting
App Store 2.4.0Waiting for review
Google Play productionRolling out to 20%

Timeline: uploaded, promoted, approved, sent for review, rollout raised, each with a name.

Made for

Leads and product owners who want one place to see where a version stands
Agencies that report release progress to a client
QA leads who sign off a version on both platforms

What it ends

Opening five tabs to answer one question about a release
Not knowing whether the Android build of 2.4 passed the readiness check
Piecing together who promoted, approved and sent what from chat history

How it works

Step 1
Open Releases on a project
Every version number your builds carry gets its own release page. The build page links to the release page of its version too.
Step 2
Read the version
Builds of that version for iOS and Android with installs, readiness and channels, open release blockers, the App Store, TestFlight and Google Play state, and the timeline.
Step 3
Act from the page
On Team, tick the checklist and give approvals for the newest build of each platform right there, and open App Store review or Play releases for the store steps.

What the page shows

The builds of the version in the project, iOS and Android, with upload date, installs, store readiness and the channels each one opens in now. The newest build per platform is the candidate, with its readiness findings listed.

The stores part shows the App Store version state and its build, TestFlight builds with internal and external testing state, and the Google Play tracks with this version and their rollout percentage. The timeline brings together workspace activity, App Store review steps, Google Play release changes and store events for the version.

Pro and Team

Pro sees the page read only: builds, readiness, channels, blockers, store state and the timeline. Team adds the release checklist and named approvals of the candidate builds, with ticks and approvals from the page.

From the CLI and AI tools

appforshare release list shows the versions of an app and appforshare release status 2.4.0 prints one release in the terminal. The CI API has the same at /api/ci/releases, and AI tools connected through the MCP server read it with release_overview. All of them only read.

Good to know

The store state is the one from the last status check, with its time shown. It is not a live view of App Store Connect or Play Console.
A release is a version number. Builds without a version number are not on a release page.
Approvals are given in the dashboard only, never from the CLI or the MCP server.

Questions

Do I have to create a release?: No. Every version number your builds carry has a release page already. Nothing extra is stored.
Does it work without a store connection?: Yes. Builds, readiness, channels, checklist and timeline work without one. The App Store and Google Play part needs your store connection and the app shared with AppForShare.
Which plan do I need?: Team for the full page with the checklist and approvals. Pro gets the read only view.