Release Engineering
Builds and Platforms
Prepare clean, tested builds for each supported platform. A good build is installable, predictable, signed where required, free of secrets, and documented clearly for players.
- Targets
- Web, Android, Windows
- Review
- Gallifai scan
- Risk
- External hosts
Targets
Platform Matrix
| Platform | Player Needs | Developer Checks |
|---|---|---|
| Web App/PWA | Browser support, controls, network requirement. | Test mobile and desktop browsers, loading, audio unlock, save data. |
| Android | Android version, permissions, file size, install steps. | Sign release build, remove debug logs, verify first launch. |
| Windows | Windows version, extraction steps, executable name. | Package dependencies, test on a clean machine, confirm the executable opens. |
| External host | Download availability and file integrity. | Keep links public, avoid request-access pages, replace expired links. |
Pre-Upload Checklist
- Remove development keys, admin panels, internal endpoints, and sample credentials.
- Confirm file names match the version and platform.
- Test a fresh install, not only an upgrade over your developer copy.
- Submit the final build through the normal Appsinity review flow so Gallifai can perform platform safety scanning.
- Write down known issues so the listing can disclose them honestly.
External Download Hosts
If you use Google Drive, Dropbox, GitHub, or another external provider, Appsinity does not control that provider's availability, terms, cookies, or scanning. The listing should explain where the link goes and what players should expect. Do not use hosts that require suspicious installers, forced surveys, or misleading download buttons.