The launch process
Funox uses a two-stage launch model so you can validate your game with real players before going global. This gives our editorial team and your team confidence that the game is ready, and lets you collect feedback in a low-stakes environment.
Stage 1 — Basic Launch
Your game is released to a limited audience for two weeks. During this stage:
- Monetization is disabled (no ads, no IAP).
- Only the Basic Implementation of the SDK is required.
- Funox QA performs a basic review.
- We measure average playtime, conversion to gameplay, and retention.
The goal here is to confirm your game runs cleanly across browsers and devices, and that players actually engage with it.
Basic Launch SDK requirements
At minimum, your game must:
- Initialize the SDK (
SDK.init()). - Call
gameplayStart()when active gameplay begins (recommended).
That's it. Everything else is optional during Basic Launch.
Stage 2 — Full Launch
After Basic Launch metrics meet our quality bar, your game is promoted to Full Launch:
- Released globally across Funox and our partner network.
- Monetization enabled (revenue sharing activated).
- Featured in category pages and homepage rotations where appropriate.
Full Launch SDK requirements
For Full Launch, the following are mandatory:
gameplayStart()andgameplayStop()called at the right moments- The data module for progress saving (if your game has progression)
- The user module for account features (if your game has accounts/leaderboards)
Optional but recommended:
- Loading lifecycle events (
loadingStart/loadingStop) - Banner ads on appropriate menu screens
- Rewarded ads tied to in-game rewards
Submission
Submit your game at the Funox Developer Portal. You will be asked to provide:
- A playable build URL or upload
- Game title, description, and category
- Cover art and screenshots
- A privacy statement if you collect data beyond what the SDK provides
What we look at during review
| Area | What we check |
|---|---|
| Technical | Loads under our size limits, runs on Chrome/Edge/Safari, works on mobile |
| Gameplay | Lands the player in gameplay quickly, intuitive controls, engaging core loop |
| Quality | Original assets, no broken art/audio, polished UI |
| Compliance | Age-appropriate content, no prohibited material, respects ad placement rules |
Most rejections come from missing mobile support, slow loading, or skipping the SDK gameplay events. Read the requirements carefully before submitting.