APPSINITYPublish your first app
This is the whole first release as one list, with the exact limits so you can prepare the files before you open Studio.
Open Appsinity StudioPrepare the assets first
| Asset | Spec Studio states | Hard limit |
|---|---|---|
| Icon | PNG or JPEG, recommended 512 × 512 px | 2 MB |
| Feature graphic | Recommended 1024 × 500 px | 15 MB |
| Screenshots | PNG / JPEG / WebP, or an MP4 trailer | 250 MB per media file |
| Short description | One line under the title | 80 characters |
| Long description | The About block | Capped server-side as well |
The seven review sections
Until all seven are complete the dashboard, statistics, reviews and advanced tabs stay locked. The checklist shows 0 / 7 and each row's badge reads Not started (or Not set for publishing).
- Data safety and privacy. The privacy policy link plus what the app collects, shares, stores and protects.
- Edit listing. Name, short and long description, icon, feature graphic, screenshots, category, tags and links.
- Build file. The file users install or open, with version details ready.
- App declarations. Content rating, target audience, social features, mature content and related policy answers.
- Financial declaration. Whether the app touches payments, lending, banking, insurance or crypto.
- Health declaration. Whether the app covers wellness, medical advice, symptoms or fitness tracking.
- Publishing status. Draft, live after review, or hidden.
Upload the build
Games take .apk, .aab or an exported web folder; apps take the same plus a .zip of Windows files. The upload is a single presigned PUT, so there is no pause, resume or cancel once it starts — a cancelled tab means starting the file again.
- Android: prefer
.aab. Signing runs the Android build tools on it and produces a universal.apkfor install. - Web: the folder must contain
index.html; total folder size must stay under the 5 GB ceiling. - Windows: zip it. The desktop client unpacks
.zipand looks for the first executable up to three folders deep.
Deploy and check
- Deploy to production. Press the button in the Preview & deploy grid. Status becomes
published. - Open the live URL. Copy it from the ? View App link, then load it in a normal browser, not the dashboard.
- Check the download. On an Android device for an Android build. On a PC you should now see the Will not install on your Windows PC note, and that is correct.
- Check the rails. Search for the name in the store header, and look in your category page. New Releases needs a fresh date, Top Charts needs traffic.
- Ask for the first reviews. The rating block shows New until a review lands.
Immediately after
- Watch Analytics → Visits and Downloads for the first 48 hours. A listing with visits and no installs is a description problem, not a traffic problem.
- Answer reviews. The reply box is the only support channel on the listing.
- Do not edit the name repeatedly after launch: spam policy treats title-switching as keyword stuffing.
Frequently asked questions
Can I publish without a build?
You can complete the listing, but the download chain resolves to nothing and the button reads Unavailable. Use pre_register instead if you want to collect interest before the file exists.
Does the first release need a version number?
There is no separate version-code field in Studio. The version in the storage key comes from the upload path or a timestamp, so keep your own release numbering inside the build.
What is the single most common first-release mistake?
Publishing an Android .apk and expecting Windows visitors to install it. Read Windows builds before you advertise to PC players.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]