Export
Create a release build for the target platform. Test it on a clean device or browser profile.
Developer Studio
Publishing Guide
Publish a game on Appsinity by preparing the build, writing honest metadata, adding media, choosing platform and age details, passing safety review, and maintaining the listing after release.
- Step 1
- Prepare build
- Step 2
- Create listing
- Step 3
- Submit review
- Step 4
- Maintain release
Workflow
Full Publishing Flow
Clean
Remove debug files, private keys, test credentials, internal URLs, and unfinished developer-only tools before submission.
Document
Write accurate descriptions, controls, permissions, known issues, and age guidance.
Submit
Upload or link the build in Developer Studio, then submit for review. Gallifai handles Appsinity safety scanning.
Listing Fields
| Field | What to Enter | Good Standard |
|---|---|---|
| Title | Official game or app name. | Short, unique, no impersonation. |
| Short summary | One or two sentence pitch. | State genre, action, and platform clearly. |
| Description | Long player-facing explanation. | Include controls, features, modes, limits, ads, and download notes. |
| Category | Closest gameplay or app type. | Pick the category players would expect. |
| Platform | Web, Android, Windows, or other target. | Match the actual uploaded build. |
| Age rating | Audience suitability. | Rate for the strongest content, not average tone. |
Media Requirements
Icons, banners, screenshots, and trailers should show the real product. Avoid fake concept art, unrelated cinematic scenes, misleading UI, hidden watermark theft, or images that include private information. Screenshots should be sharp enough for players to inspect gameplay.
- Use one clear square icon that remains readable at small size.
- Use screenshots from actual gameplay or app screens.
- Show core interaction, menus, modes, and visual style.
- Do not show claims like "official", "verified", or "number one" unless Appsinity granted that status.
Review Readiness Checklist
- The game launches without editor-only files or missing dependencies.
- External download links are public and do not require players to request access.
- The description mentions ads, online features, data collection, and permissions where relevant.
- The build does not include malware, miners, spyware, credential prompts, or hidden installers.
- The listing does not copy another developer's brand, screenshots, name, or copyrighted assets.
After Publication
Publishing is not the end of responsibility. Monitor reviews, keep support available, replace broken links, remove old unsafe builds, and update metadata when gameplay, ads, permissions, file size, or platform compatibility changes.