Tyrbo Make your game

A mobile game engine that starts from the phone, not from a desktop

A phone is a strange machine to build games for. The screen is small and covered by the player's own thumbs. Sessions start at a bus stop and end when a message arrives. The hardware ranges from new flagships to handsets several years old with little memory to spare. An engine that treats all of that as an afterthought produces games that feel cramped, drain batteries and stutter on the phones most people carry.

Tyrbo's engine is mobile from the first decision. Every game picks one orientation, controls are planned around what a thumb can do, and the finished game is checked on a low-end Android phone. Android with Google Play is the first store.

Make your game

Sign in to get the plan and its concept art. Both are free.

  • Match-3 puzzle game concept art in the bright and bold lookMatch-3 puzzle · Bright and bold
  • Survivors game concept art in the 16-bit pixel lookSurvivors · 16-bit pixel
  • Platformer game concept art in the 16-bit pixel lookPlatformer · 16-bit pixel
  • Top-down adventure game concept art in the 16-bit pixel lookTop-down adventure · 16-bit pixel
  • Tower defense game concept art in the bright and bold lookTower defense · Bright and bold
  • Runner game concept art in the bright and bold lookRunner · Bright and bold
  • Cozy farm and garden game concept art in the cozy cartoon lookCozy farm and garden · Cozy cartoon
  • Card battler and autobattler game concept art in the gilded fantasy lookCard battler and autobattler · Gilded fantasy
Looks Tyrbo starts games from. Every game ends up with a look of its own.

What a phone asks of an engine

Building for phones changes the engine's priorities. A few constraints shape nearly every decision:

  • The thumb is the controller. Touch has no buttons to feel for and no hover state. Targets must be big, spaced, and kept away from the edges where gestures live.
  • One hand, often. Portrait games are frequently played with a single thumb, which limits how many things the player can do at once.
  • Interruptions are normal. A call, a notification or a locked screen can stop play at any moment, so progress has to be kept as the game goes.
  • Hardware varies enormously. The same game has to hold up on modest chips and limited memory, not only on the newest model.
  • Sessions are short. A round that needs ten quiet minutes rarely gets them.

An engine that respects these produces games people keep installed.

One orientation per game, chosen in the plan

Many engines let a game rotate freely, which means every screen has to be designed twice and usually ends up compromised once. Tyrbo settles the orientation during planning, portrait or landscape, and builds the layout, the camera and the controls around that one shape.

Portrait suits one-thumb play: runners, puzzles, idle games, most casual ideas. Landscape suits games that need width, such as racing or a side-view platformer with room to see what is coming. The planning question arrives with a suggested answer based on your idea, and you can override it. Once chosen, nothing in the game is stretched to fit another shape.

Touch input, planned around thumbs

Input is the job where desktop thinking does the most damage. A virtual keyboard of eight on-screen buttons may work on a monitor with a mouse; on a phone it is a mess of missed taps.

Tyrbo plans controls from the gesture outward. A tap or a hold for one-handed games. A swipe or drag for lanes, aiming and sorting. A virtual stick when a hero needs to roam an arena, built on the free movement brick. Buttons get room, readable labels and distance from the edges, and the plan says how each one behaves before anything is built. If a control feels wrong in your hand, describe what you want, and the next build reflects it.

Low-end hardware sets the budget

On phones, the floor matters more than the ceiling. A game tuned on a flagship can overheat or crash on older devices, and those players leave quickly.

Tyrbo treats low-end Android as the target, not an afterthought. Physics is added only when a design has bodies that fall, bounce or collide, so a puzzle that runs on rules alone carries none of that weight. Art detail, effects and the number of moving things are scoped with the modest phone in mind, and every game must run on low-end Android before it leaves the pipeline. The same check confirms there are no soft-locks, so an interrupted player never comes back to a dead end.

The store side, already in the engine

A mobile game also has to pay its way and give players a reason to return, and those pieces shape the loop. Each game arrives with ads and in-app purchases wired and leaderboards live, so a rewarded video or a starter pack is a design choice you make in words rather than an integration project at the end. You decide how much, or how little, of it the game uses.

The finished game is a signed Android build you own, with a checklist for Google Play. For the step-by-step view from idea to store, see the mobile game maker, the guide to making a mobile game without coding, or the Android game engine page for what the build itself involves.

Ideas you could type

  • A one-thumb portrait game where you hold to inflate a balloon and release to float past spikes
  • A landscape skate game on rooftops where you swipe up to grind rails and down to duck under signs
  • A pocket bakery where you tap ovens before the bread burns and hire helpers as orders pile up

From a sentence to your phone

  1. 1

    Describe it

    One sentence is enough. Say what you tap, what you dodge, what you win.

  2. 2

    Answer a few questions

    Each comes with our best guess picked, so most of the time you just tap Continue.

  3. 3

    See the plan

    A title, a pitch, every part of the game, and concept art, before anything is built.

  4. 4

    Play it today

    Scan the code and it runs on your phone. Change it by talking to it.

Built to ship, not just to prototype

Every game leaves the pipeline with all of this checked, not hoped for.

  • No soft-locks
  • Runs on low-end Android
  • Ads and purchases wired
  • Leaderboards live
  • A signed build you own

Questions people ask

What makes a game engine a mobile game engine?

Its defaults come from the phone: touch input sized for thumbs, one orientation per game, short sessions, interruptions and modest hardware. Tyrbo plans every game around those from the start and checks each one on a low-end Android phone.

Can a Tyrbo game switch between portrait and landscape?

No. Each game picks one orientation during planning, and its layout, camera and controls are built for that shape alone. Choosing once is what lets every screen fit properly instead of being a compromise between two.

Will a game from this engine run on older phones?

Running on low-end Android is one of the checks every game must pass before you get it. Physics, effects and art detail are budgeted with modest hardware in mind, so the game is not tuned only for new devices.

Which mobile stores does the engine build for?

Android first, with Google Play as the store. Every finished game comes as a signed Android build that you own, along with a step-by-step checklist for publishing it.

Your game is one sentence away.

Make your game

Sign in to get the plan and its concept art. Both are free.