Workspace access and submission requirements
The developer workspace is limited to the existing platform account allowlist. Player sign-in remains available to everyone. New submissions and new updates use submission requirements version 2; requirements cannot be downgraded to bypass validation. Existing published games and saved drafts are retained.
Complete the required fields shown in each step. Package or field errors must be corrected in the same draft before submission. The platform validates the package and operates the player, review and publication workflow. Developers supply working game controls, responsive layouts and accurate device declarations; the platform does not rewrite incompatible games. See package and media requirements and Basic and SDK integration requirements.
Upload → QA → Details → Submit
Start with a playable Web build. Create a draft, upload the build, test it in QA, complete its details and cover, then submit it for review. An upload or an approved draft is not yet a published game.
- Create your first submission
Choose the game identity and save your draft before uploading.
- Prepare and test the build
Check package limits, cover assets and every device you support.
- Review and release
Address feedback, publish an approved trial and provide evidence for full launch.
Returning to a game?
Use a game build update for a new version, or a listing update for its cover and game-page details. Keep the existing game address.
Integrate at your own pace
Choose Basic to submit a playable browser export without a platform SDK or game contract. Choose SDK when you need platform lifecycle or checkpoint integration. Integration mode is separate from Trial or Full launch visibility. The FoolFish SDK 1.2 connects loading and gameplay events. Games with progress can add browser and account checkpoints. A pause menu and a save system are not required. Advertising and revenue-sharing APIs are not active.