Browser game example
This run starts at a steady pace, then asks for quicker jumps as the score grows. Coins add a reason to take small risks, while the rooftop skyline gives the route a clear setting instead of an endless blank track.
The sample can be viewed from the side or from behind the runner in a retro 3D scene. Both views keep the same tap-to-jump rhythm, making it easy to compare how camera position changes the feel of a familiar obstacle course.
Cleo is opening to founders in small batches. Join the waitlist and we'll save your spot.
Updated
This run starts at a steady pace, then asks for quicker jumps as the score grows. Use the sample to name the audience, the main action, and the smallest useful first version. Cleo HQ then helps turn your own brief into a product plan and a working build.
The runner moves automatically, and obstacles speed up as the score climbs. Coins tempt players to adjust their timing while they avoid hazards. The rising pace creates a natural short-session loop: start, react, beat a previous score, and try again when the run ends.
Players can jump with a tap or click, or use keyboard controls on a computer. The same action works across the side-on and retro 3D views. If you build a runner for a particular audience, choose controls that fit how they hold the device and leave enough space for the play area.
A skyline gives obstacles and collectibles a shared place in the world, so the course feels like a journey rather than a score screen. You could set your version in a forest, a station, or a changing city block. Keep the route readable as the pace rises, especially on a phone.