Choose how you want to enter the idea
Draft the main rules with the on-screen keyboard, or attach a hardware keyboard if that suits your setup. Keep the prompt organized around what the player does and what ends the round. A text accessory can make editing easier, but it does not change the game controls your generated version should present to a player.
Test both direct touch and intended controls
On a wider iPad layout, chat and preview can appear beside one another; on a narrower layout, switch between Chat and Playtest. Play with a finger and, if your design expects it, with a stylus or keyboard. Confirm that the game gives clear feedback after each selection and that important targets do not become too spread out on the wider display. Rotate the iPad and test again if the intended play layout changes with orientation.
Pick an editor if you need a native project
For a prompt-led version, use Chat to ask for one change and Playtest to inspect it. If you need project files and a platform build, GDevelop's official iPhone/iPad guide describes its own on-device editor and export path; check the current app listing and requirements before relying on it. Choose a workflow based on the artifact you need, not just the size of the screen.
Try the published Stack game as a reference for a simple tap action, then ask whether your own mechanic needs precise dragging, repeated taps, or keyboard input. Test the actual gesture rather than assuming tablet touch will feel like a mouse.
Questions about make games on iPad
Does making a game on an iPad automatically make it an iPad app?
No. A prompt-led version is a public playable game. Native app packaging and store submission require a workflow that specifically supports those deliverables.
Should I design separate iPad and phone layouts?
Decide from the interaction. A centered board may work at both sizes, while a wider map may need a deliberate layout adjustment. Test both screen sizes and orientations you intend to support.