Make the next move worth playing.
Plan a playable browser or touch-first game with progression, restart controls and an optional managed account leaderboard, then measure target-device performance.
Review the prepared brief in Studio. A build starts when you send it.
Specify the loop, not just the scene
Name what the player controls, how the world changes and what advances a run. A coherent brief includes escalating difficulty, a clear goal, pause, restart and an end state. Keep the game state, overlay controls and score display coordinated so restarting cannot leave a stale timer or duplicate input listener.
Choose how much authority a score needs
A personal score history and a competitive public leaderboard have different trust needs. Client-reported scores are unsuitable for prizes without an authoritative validation design. Separate public display fields from private player records and state whether offline runs are retained. Test touch input, keyboard controls and reduced-motion alternatives.
Give each screen its own job.
These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.
Web
A playable canvas with keyboard controls and authored menus.
Mobile
Touch controls, safe-area review and a layout that keeps play unobstructed.
Desktop
A wider game presentation or an authorized score-review workspace.
Plan the records and their owners.
Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.
| Collection | Suggested fields | Access to decide |
|---|---|---|
scores | player, mode, score, created_at | Declare which score fields can be public and who can submit. |
player_profiles | owner, display_name, preferences | Self-only profile editing. |
Verify the outcome, then expand.
- Complete a run, lose, restart and confirm all gameplay state resets.
- Verify keyboard and touch controls on their intended devices.
- Measure frame time and responsiveness during a demanding scene.
- Test score access rules and document client-reported score limitations.
From this brief to your first version.
Review the proposed workflow
Start with this editable blueprint brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.
Build and check the result
Review the isolated preview and execute the checks listed on this page. Begin with A playable canvas with keyboard controls and authored menus. Resolve missing service setup and save verified progress before expanding the scope.
Connect or export when ready
Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.
Make the starting point your own.
Questions before you build.
Does the game automatically run at 60fps?
Performance must be measured on the target device and scene. Frame rate depends on generated code, assets, graphics and hardware.
Can I use scores for paid prizes?
A client-reported leaderboard needs a separate authoritative validation and abuse-control design before it can support money or prizes.