Skip to content

The launch process

AI Summary

A short gist of this page, generated for you.

Powered by AI. Summaries can miss nuance — when in doubt, read the page.

Every game follows the same path: you upload a build, prove the SDK integration in the portal's preview, and submit it. Our QA team then tests it and either approves it or tells you exactly what to fix.

#The steps

Step What you do Where
1. Create an account Sign in with Google, GitHub or Discord Developer Portal
2. Integrate the SDK Add the script and the four required calls SDK overview
3. Upload your build Fill in the game details and upload the game folder Portal → Submit Game
4. Pass the SDK checklist Play the build in the preview until all four checks are ticked Portal → your game
5. Submit for review Send the build to QA Portal → your game
6. Fix what QA reports Upload a new build and submit again Portal → your game
7. Go live Nothing — we publish the game once it is approved —

#What you upload

The Submit Game form asks for:

  • Title and description
  • At least one category
  • The engine the game was built with
  • Orientation — landscape, portrait or both
  • The game folder — your web build with index.html at its top level, 100 MB or less in total
  • A square logo (1:1, up to 5 MB)

A new game starts as a Draft. Nothing is sent to QA until you submit it.

#The SDK checklist

Before you can submit, the portal has to see your build make these four calls:

Check When your game should call it
FunOxSDK.init() Once, when the game starts
FunOxSDK.gameplayStart() When active play begins
FunOxSDK.gameplayStop() When play ends or is interrupted
FunOxSDK.commercialBreak() At a natural break, such as between levels

Each check ticks itself the first time the build makes the call in the preview. They cannot be ticked by hand, and they reset for every new build you upload.

Tip

Play one full round in the preview: start the game, play, reach a break, finish. That is normally enough to tick all four.

#Statuses

Your game always has one of these statuses in the portal:

Status Meaning What you can do
Draft Uploaded, not yet submitted Edit details, upload builds, submit
Pending Review Waiting for a QA tester Wait
In QA Review A tester is playing your game Wait — the build is locked
Changes Requested QA found issues Fix them, upload a new build, submit again
Approved Passed QA, waiting to be published Wait — the build is locked
Live / Published Players can play it Track analytics and revenue
Rejected Not accepted in its current form Read the reason, then rework and submit again

#What we look at during review

Area What we check
Technical Loads quickly, runs on Chrome, Edge and Safari, works on mobile — see technical requirements
Gameplay Gets the player into the game fast, intuitive controls, an engaging core loop
Quality Original assets, no broken art or audio, polished UI
Ads Ad breaks at natural pauses only — see advertisement requirements
Compliance Age-appropriate content, nothing prohibited
Most common reasons a game comes back

Missing mobile support, slow loading, and SDK calls at the wrong moment — for example gameplayStart() on the loading screen. Read the requirements before you submit.

#After launch

Once the game is live, the portal shows its analytics and revenue. To change a live game — ship an update, ask a question or request its removal — use the options on the game's page in the portal. A new build goes through the same checklist and review.