Publishing
Review process
Every version of every game is reviewed by a person before players can open it, including updates to games that are already live. Approval applies to that exact build only. Each version on your dashboard shows a timeline of the stages below.
Stages
| Stage | What happens | Who |
|---|---|---|
| Uploaded | The ZIP and media arrive with the version label | You |
| Media processed | Cover, icon, portrait, screenshots and video are checked against the media rules and converted | Automatic |
| Files checked | The ZIP is unpacked and checked against the file rules | Automatic |
| Quality report | Automatic checks run (see below). Each version gets a fingerprint of its files and media | Automatic |
| Submitted for review | You chose Submit for review. The version joins the review queue | You |
| Reviewer recommendation | When a reviewer is assigned: they play the build and recommend a decision, with notes | Review team |
| Live, Changes requested or Rejected | The decision, with written feedback | Platform owner or admin |
If the media or file checks fail, the upload is refused with the reason and nothing is kept. Fix the problem and upload again. If a quality check fails, the version is kept as a draft but cannot be submitted.
Automatic quality checks
Open Quality report on a version to see these. A version with a failed check cannot be submitted.
| Check | Result |
|---|---|
Root index.html exists | Pass or fail |
| Archive safety validation completed at upload | Pass or fail |
| Cover image is present | Pass or fail |
| Control instructions are present (at least 10 characters) | Pass or fail |
| Supported devices are declared | Pass or fail |
| No private keys or access tokens in text files | Fail if one is found |
| Media files are present and unchanged | Fail if any is missing |
| Build files, metadata or media unchanged since upload | Fail if anything changed |
| SDK behaviour | Manual: tested by the reviewer |
| Runtime and gameplay | Manual: a human playtest |
| Rights and content | Manual: reviewed by a person |
The report also lists warnings for the reviewer: every outside web address found in your code, use of the camera, microphone or location, and text files too large to scan. Warnings do not stop submission, but the reviewer will ask about anything you have not declared.
You can re-run the quality checks up to 5 times an hour.
What the reviewer tests
The reviewer plays the exact build in the real player frame, on the devices you declared, and completes this checklist before a version can be approved:
- Loads and retries correctly. The game loads to a playable state, and reloading works.
- Controls, devices and orientation. The controls match How to play, and the game works on each declared device and in the declared orientation.
- Save and resume. Progress behaves as the listing says: account saves follow the account, guest saves stay separate, nothing is lost or mixed between players.
- Sound, mute and pause. The site's mute and pause stop sound and gameplay (or, without the SDK, the game has its own controls).
- Content and outside behaviour. The content matches the declarations, and the game contacts only its declared outside addresses.
- Rights. The game and its media appear to be yours or licensed, and the listing is accurate.
The reviewer also checks the Review and rejection policy and the Content rules.
Decisions
| Decision | What it means | What you can do |
|---|---|---|
| Approved | The version goes live and replaces the previous live version. Its media appears on the site | Nothing. Upload a new version for any change |
| Changes requested | Something must be fixed. The feedback says what | Upload a fixed version and submit it. You can also resubmit the same version if the feedback concerns something outside the build |
| Rejected | This version will not be published. The feedback says why | Upload a new version that addresses the reason, or appeal |
Every decision other than approval comes with written feedback of at least a sentence, shown on the version in your dashboard. You get a notification when a decision is made.
Who reviews
Reviews are done by the Smaz Games team. Reviewers can recommend a decision; the platform owner or an admin makes the final decision. Reviewers are never assigned their own games and cannot review them.
How long review takes
There is no fixed review time and no guaranteed date. Games are generally reviewed in the order they arrive. Approval is not guaranteed, and an approved game is not guaranteed a place on the homepage or in featured lists.
Before you submit
- Test the uploaded build in its Private preview, on each device you declare.
- Read the quality report and resolve every failure.
- Check that the description, controls, devices and declarations match the build.
- If your game uses outside servers, make sure they are running: the reviewer will use them.
- If something needs explaining, such as how to reach a later level, put it in How to play or contact developer support.