APPSINITYAppsinity Store overview
Appsinity Store is a digital distribution platform for Android builds, Windows builds and browser-playable web games. This page maps every surface you publish to and the pipeline your build travels through.
Open Appsinity StudioThe four surfaces you publish to
There is no single "Appsinity app" that everything lands in. Your listing is reachable from four places, and each one pulls from the same document in the store catalog.
| Surface | Address | What it shows |
|---|---|---|
| Games store | appsinity.com/Games/store | Rails: Popular Categories, Editor's Picks, Because You Played…, Trending Now, New Releases, Top Charts. |
| Apps store | appsinity.com/Apps/store | Popular Categories, Editor's Picks, New Releases, Top Charts. No "Because You Played…" and no Trending rail. |
| Listing page | appsinity.com/Games/store/listing/<slug> and /Apps/store/listing/<slug> | One shared template: hero gallery, trailer, About, Data safety, Reviews, and the buy panel on the right. |
| Desktop client | Appsinity-Setup.exe (Windows) | Browses the same website in an Electron shell, and installs Windows releases into a local library. |
From upload to a live listing
- Register. Create a developer account at studio.appsinity.com and verify the email address with the 6-digit code.
- Create the project. The Studio wizard creates a draft dashboard, which is private to you and your team.
- Fill the seven review sections. Data safety, listing, build file, content declarations, financial declaration, health declaration and publishing status. Until they are complete the dashboard, statistics, reviews and advanced tabs stay locked.
- Upload the build. Files are PUT straight to
storage.appsinity.com/public/…through a presigned URL. See Upload limits and file types. - Sign it. Android builds are signed server-side with the Appsinity key. See App signing.
- Deploy to production. Set publishing status to
published. The store catalog only returns documents whose status is exactlypublished.
What actually makes something visible
The store catalog filter is deliberately strict: a listing is published only when status === "published" and it is not a pre-registration. Everything else — draft, unpublished, closed_testing, suspended, banned — is invisible to visitors.
A pre-registration listing is a separate case: preRegisterEnabled (or preRegister.enabled) keeps it out of the catalog rails, and it is reachable only through a direct link, where it shows a Pre register button instead of a download.
status in Studio is the only switch that publishes. There is no separate "submit for review" or "go live" endpoint, and no manual approval queue — the field takes effect on save.What Appsinity does not do today
Documenting these honestly matters more than documenting them aspirationally. If a feature you need is missing, email [email protected].
- No paid downloads, no in-app purchase SDK and no subscription manager. Every listing's buy panel is hard-coded Free; monetisation is CPM on listing visits.
- No iOS path at all:
.ipais on the upload blocklist. - No public API keys, OAuth applications or webhooks.
- No crash-report ingestion. Analytics counts store events, not exceptions from your build.
- No wishlist, cart or offers — those header icons are placeholders.
Frequently asked questions
Do I need a separate account for the store and for Studio?
One Appsinity identity works for both, but they are different account types. A player account (accountType: "player") signs in at /user/login.html to download, review and follow. A developer account signs in at Studio to publish. See Player accounts.
Is there a review or approval wait?
Not an enforced one. Publishing is a status field you control, so a listing can go live the moment its build and declarations are complete. Policy enforcement is retrospective: listings that breach content policy can be set to suspended or banned.
Which URL do I share for my app?
The clean listing URL, for example https://appsinity.com/Games/store/listing/my-slug. Both the Games and Apps prefixes resolve through the same template; the mode is chosen from the path.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]