Submission checklist
Run through this list before every submission. Each item is a common reason for rejection and links to the full requirement. Passing it doesn’t replace the requirements, but it catches the issues reviewers flag most often.
- The game name matches the Developer Portal. The title shown in‑game is identical to the game name registered in the FRVR Developer Portal. See Trust & safety.
- Sound settings persist across restarts. Mute, volume, and music / SFX toggles are restored after the game is closed and reopened. See Integration.
- Sound stops when the game loses focus, driven by the SDK’s pause / audio hooks, not your own focus listeners. See Integration.
- External links are gated on the SDK. Privacy policy, terms of service, and any other outbound links are hidden when the channel doesn’t allow navigation. See Design.
- IAP entry points are hidden when IAP is unavailable. No store buttons, price tags, “Buy” prompts, or “Restore purchases” buttons when IAP isn’t ready. See Monetization.
- Rewarded ad entry points are hidden when no ad is available. No “Watch ad” buttons unless a rewarded ad is ready to show. See Monetization.
- No vibration / haptics toggle without web support. If the game has no working web implementation of vibration or haptic feedback, remove the setting. See Design.