Developers/Guidelines

Diretrizes para Desenvolvedores

O que avaliamos antes de aprovar um jogo.

Technical requirements

HTML5 / JavaScript only. No Flash, no server-side rendering required at runtime.
Self-contained bundle: all assets (images, audio, fonts) must be embedded or bundled. No external CDN calls at runtime.
Single entry point: index.html at the root of the ZIP. The platform loads this file in an iframe.
Maximum bundle size: 50 MB unzipped. Compress assets aggressively.
All asset URLs must use relative paths — no hardcoded domains or absolute URLs.
HTTPS-only assets when loading from external sources (e.g., self-hosted audio).

Game must be interactive within 5 seconds of loading on a mid-range device.
Mobile-friendly: touch controls or a responsive keyboard layout. No mouse-only gameplay.
No infinite loading screens or blocking splash screens without a skip option.
Game must respond to pause/resume events from the SDK lifecycle hooks.
Volume controls or audio mute support is strongly recommended.
Resolution should scale gracefully between 320px and 1920px viewport width.

No adult content, nudity, or sexually explicit material.
No hate speech, discrimination, or content targeting protected groups.
No gambling mechanics with real-money implications (loot boxes with paid currency are not allowed).
No depictions of graphic violence targeting real people or groups.
Age rating: all content must be appropriate for players aged 13 and above.
No misleading UI patterns designed to trick players into unintended actions.

SDK integration is optional but strongly recommended. Games that integrate the SDK receive priority placement and unlock monetisation features.

Call reportGameOver(score) at the end of every session — required for leaderboard eligibility.
Use saveProgress / loadProgress for persistent state instead of direct localStorage access.
Ad placements (showRewardedAd, showInterstitial) must be triggered by a user action, not automatically.
Track events must use lower_snake_case names and avoid collecting personally identifiable information.

Review timeline: 3–5 business days after submission.
You will receive an email confirmation when your game goes live.
Rejected submissions include a reason. You may resubmit after addressing the issues.
Games that repeatedly violate guidelines will be suspended from the platform.
Minor bugs found after approval can be corrected by submitting an updated ZIP.