Mobile Readiness Checklist

RetiPie discovery is mobile-first. Use this checklist before submitting a new release for review.

First screen

• Show the core action quickly.
• Avoid long desktop-style menus before the first playable moment.
• Make the main control visible without requiring instructions.
• Render a meaningful first frame so runtime poster capture has useful pixels.

Controls

• Use touch input as the primary path.
• Keep tap targets separated enough for thumbs.
• Avoid hover-only interactions.
• Make pause, restart, and mute controls reachable.

Layout

• Test narrow and tall phone sizes.
• Keep gameplay readable when the browser viewport changes.
• Avoid fixed desktop canvas sizes unless you scale them deliberately.

Runtime signals

• Send loading progress if your game has a visible loader.
• Don't write code to stop your game when the player swipes away or backgrounds the app: RetiPie freezes timers, animation frames, and Web Audio for you (pause HTML media elements yourself). Use retipie.game.pause() only for your own pause menu.
• Call gameplayStop() when a run ends, and gameplayStart() when the next one begins.
• Declare leaderboard support from code when the release supports scoring.
• Answer the age rating questionnaire honestly at upload; it decides who can play.