Your first game does not need an open world, multiplayer servers or a shop. A useful prototype can let a player move around one 2D scene, collect five objects and receive an unmistakable completion message. GDevelop provides visual events, objects and ready-made behaviours for this kind of project, as its official platformer tutorial demonstrates. Yet no-code does not mean no logic, no debugging or automatic quality. The workflow below is an editorial design exercise with verifiable acceptance criteria, not a claim that we built and tested the resulting game ourselves.
1. Define a finishable loop before choosing graphics
Write a one-page scope: one player, one scene, five collectible objects, a visible score and a completion state. The player should understand the objective without an explanation from the developer. Avoid enemies, an account system, an inventory and online rankings in version one. The primary acceptance test is behavioural: a new player can move, collect all five objects and recognise that the round is finished. Attractive artwork is helpful, but it cannot compensate for an unclear objective or a broken input mechanism. Use text or symbols as well as colour to communicate progress.
For planning, imagine four practice sessions of 45 minutes each: build the scene, add movement and collision, implement score and completion, then test and export. This is a hypothetical schedule, not a measured productivity claim. If movement is still unreliable after session two, stop adding new features and investigate the cause. A narrow scope leaves enough time to examine failure cases and write down what changed. Keep a short change log so a working version can be recovered after an experiment goes wrong.
2. Create the scene, objects and behaviours
Start a new GDevelop project and make a main scene. Add a Player object, five instances of a Collectible object, a ScoreText display and a WinText message initially hidden from view. Meaningful object names matter because the visual event sheet will refer to them repeatedly. Choose a built-in movement behaviour suitable for the intended perspective, such as top-down movement, rather than manually assembling low-level movement rules before understanding the engine. The official GDevelop tutorial separates scenes, objects, behaviours and event logic, which is a useful mental model for beginners.
Place all five collectibles where the player can reach them, and check that collision shapes correspond reasonably to the visible artwork. Begin with original simple shapes or assets whose licence you have actually read. A free download is not automatically permission to redistribute every sound or character. Maintain a small asset ledger containing the creator, source, permitted use and attribution requirement. Save the editable project and a backup separately from any exported game files. A web build intended for players is not necessarily a safe replacement for the editable project source.
3. Make collision events count exactly once
Create a score variable initialised to zero at the start of a round. Add an event whose condition checks whether Player collides with Collectible. When that condition is met, increment the score by one and delete the specific collected instance. Then update ScoreText to display the current score. Deleting the instance is important: otherwise a collision may remain true over several frames and inflate the counter. The precise event configuration should be checked in GDevelop's preview rather than assumed from a written tutorial. Keep the initialisation, collection and completion events separate for easier debugging.
A second event can show WinText when the score reaches five, and optionally stop further movement or input according to the intended design. Consider edge cases before adding polish: can two objects be touched during the same frame, and could the completion message be triggered repeatedly? Does restarting a round reset the score and restore the five objects? Test one change at a time. A prototype is only reproducible when someone else can describe the condition that triggers each visible result, not merely say that the game appeared to work once.
4. Design controls for actual players and devices
State the keyboard controls on the opening screen and try them with a physical keyboard. If mobile play is in scope, loading the scene on a narrow display is not sufficient: test touch controls, hit targets, screen orientation and the location of the score. Tiny buttons can be hard to operate, while a score label hidden behind a virtual control makes feedback confusing. It may be sensible to complete a browser prototype first and then decide whether a phone version needs a different control scheme. Do not describe mobile support as verified until it has been tested on a device.
MDN's independent accessibility guidance explains why interactive web controls should be operable from a keyboard and why visible focus matters. Those recommendations are especially relevant to the game's menus, start and restart buttons, and surrounding page. They do not guarantee that the entire game is accessible to everyone. Avoid instructions conveyed by sound alone or by one colour. Ask a tester unfamiliar with the project to explain what each control does, then record the confusion before offering assistance. That feedback is more useful than the developer repeatedly playing a familiar level.
5. Test with a reproducible checklist, not intuition
Write a test case for each critical rule: score starts at zero; movement responds in every intended direction; a collected object disappears; each object increases the score exactly once; untouched objects remain; the completion message appears at five; and restart clears the previous round. Add edge cases for the scene boundary, browser refresh, small windows and missing audio. For each case record expected behaviour, observed behaviour, date and pass or fail. An unchecked box is not a failure, and an untested case should never be marked as passed merely to finish the checklist.
A modest release gate might require every critical case to pass in one desktop browser and, if mobile is promised, a real phone touch test. This is a proposed quality rule, not a certification standard. A single successful browser run does not prove universal compatibility. If a collision mask lets the player overlap an object without collecting it, adjust the mask and rerun the same test. If the exported build behaves differently from the editor preview, log that discrepancy as a separate defect. The point is to make failures observable and fixes repeatable.
6. Export responsibly and improve one thing at a time
GDevelop's publishing documentation describes web and other exports. The independent itch.io creator guide explains that a multi-file HTML5 game can be uploaded as a ZIP archive containing index.html and the necessary assets, with file-name case and relative paths handled correctly. Test the actual exported package before sharing a public link; the editor preview alone does not validate deployment. Check missing images, sound loading, navigation and input after the export. Review the hosting service's account, privacy and intellectual-property terms rather than assuming that every destination has identical rules or accepts every build.
Publish a candid description of what the prototype does, which devices were actually tested and what limitations remain. Attribute third-party assets according to their licences and never imply that GDevelop endorses the game. Collect a small amount of specific feedback, such as whether the completion state was clear or touch buttons were large enough, without inventing download numbers or user reviews. Choose one improvement for the next version and retest the original checklist. A small, documented prototype can teach more about game development than a large unfinished project presented as a commercial success.
Official resources
- GDevelop official documentation — Platformer Tutorial, Part 1 and collectible-coins series (checked 29 October 2026) ↗
- GDevelop official documentation — Publishing games to the web and other platforms (checked 29 October 2026) ↗
- MDN Web Docs — Keyboard accessible, independent web-accessibility guidance (checked 29 October 2026) ↗
- itch.io official creator documentation — Uploading HTML5 games, ZIP and index.html requirements (checked 29 October 2026) ↗
No online income or trading system guarantees profits. Results depend on skills, costs and circumstances.
Disclaimer ↗