Draft a phone-friendly first request
Write one action, one goal, and one outcome for a mistake. For example, ask for a marker that moves between two safe pads with a tap, a goal of reaching five pads, and a restart that restores the same pattern. Avoid typing a long feature list on a small keyboard; add another system only after the first loop is understandable.
Use the Chat and Playtest tabs as a cycle
Send the prompt and follow the build status in Chat. When a version is playable, switch to Playtest and try the exact action you described. Notice a concrete mismatch—such as the target being hard to see—then switch back to Chat and ask for one targeted correction. A new version starts from the latest successful version, while earlier successful versions remain available to play.
Check touch before adding detail
Try the opening with one thumb and the phone in the position you normally use. Check that the target is easy to tap and that a restart does not obscure the play area. After dismissing the keyboard, inspect the playable view: do the instructions fit, and can you reach the main action without covering an important cue? If you need a visual reference for a single-action game, try Stack and study how its tap-to-drop rule is presented.
Published versions are public. Keep private details out of a prompt and check the title and game text before sharing the result.
Questions about make games on your phone
Can I make a game on a phone without a computer?
You can describe, generate, playtest, and revise a game in the mobile creation flow. Creating a version requires Creator, and the finished game is a public playable version rather than a promise of a native store package.
What should I type first?
Start with what the player does, what they are trying to complete, and what a mistake changes. A small testable loop is easier to judge on a phone than a long list of ideas.