APPSINITYRollout and updates
There is no percentage rollout control, no phased release and no server-side distribution schedule. A saved build is available to every visitor immediately.
Open Appsinity StudioWhat is absent
- A rollout percentage on the build or listing.
- A pause/resume control for a release in progress.
- A halt on crash signals — nothing ingests crashes, so nothing can halt.
- Any way to serve version A to 10% and version B to 90%.
- Automatic delivery to already-installed copies.
Approximations that actually work
The honest recommendation for a large release: ship the code dark and turn it on server-side. That gives you a pause control that Appsinity does not.
| Approach | How you do it | What it gets you |
|---|---|---|
| Sequential gate | Keep the listing at closed_testing, send the link to a small group, then publish | A real staged cohort, by hand |
| Pre-registration | Publish interest first, flip at the launch moment | A controlled start time, no partial distribution |
| Own the flag | Ship a build whose new features are switched by a remote value you control | Rollout inside one artefact — the closest true equivalent |
| Short unpublish window | Unpublish, watch error reports, republish | Stops new installs; does nothing for installs |
Getting an update to existing players
Nothing pushes an update. Players receive a new version only when they download the listing again, and the desktop client does not re-check installed titles.
So an update that fixes a crash needs your own notification: a prompt inside the build, or a line in the short description. Both are more effective than waiting for re-downloads.
- Check the manifest version code yourself at startup and print "update available" — you have the store URL to point at.
- Reply to the reviews reporting the bug with the fix version.
- Do not delete and re-create the listing to force a fresh download; that destroys reviews and history.
Frequently asked questions
Why no staged rollout?
The store has no install telemetry from devices — downloads are counted, opens are not — so it cannot halt a rollout on real data. It is a missing feed, not a missing switch.
Does the desktop client update my game?
No. It unpacks and launches what is in the library folder and never re-validates it.
Can I at least pause a release?
Yes, by unpublishing. It takes effect in the catalog rather than instantly in every browser cache.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]