Mobile game maker: the desktop kind, and why that is normal

The first kind runs on the phone itself. You tap together a game on the device it will be played on. These are pleasant, immediate, and limited by the fact that a phone screen is a small window and a finger is a blunt instrument. They generally produce simple games inside the tool's own player.

The second kind runs on a computer, produces a project you own, and treats the phone as a target rather than a workshop. Everything commercially shipped is made this way, for the boring reason that game development involves a great deal of precise arrangement and comparison.

Flockbay is the second kind. It is a desktop application for Windows, macOS and Linux, built on open-source Godot, and it is not available on a phone or in a browser.

It starts with a brief. Flockbay asks what you want one round of questions at a time, each with a recommendation, and writes down what gets built first, what comes after and what is not in this version. Nothing is built until you approve it.

Then it builds the world. In a flat game, which most phone games are, that is tile ground (the tiles, the edges and the collision follow from which cells are ground), a band of scenery behind it, and sprites at an exact position, rotation and scale. In a 3D one it is terrain, sculpted and painted, plus water, sky, weather, plants, the player controller and props. All of it is real nodes in the scene tree, not a picture of a world.

Flockbay writes the code too: how the character moves, what a tap does, what happens when the timer ends, as GDScript inside your project. Then it play-tests its own work, sending input events and reading the debugger. You never open a script unless you want to.

You play the result and decide whether it is right. That judgement is the part that stays with you. When the call is pure taste, like which cell a ledge ends on, the same world tools are buttons around the Godot editor's 2D and 3D view, and a mouse gets you the exact spot. That is one more reason the desktop matters.

More on this: Flockbay is not a VR game maker

Screen space, mostly. Interfaces have to be much larger and much simpler than on a monitor, and every control competes with the player's own thumb for the same pixels.

Then session length. Phone games get played in short interrupted bursts, which means a game that requires twenty minutes of uninterrupted concentration is being played in the wrong place. Saving and resuming stop being a feature and become the shape of the design.

And input precision. Anything requiring an accurate tap on a small target will frustrate. This pushes mobile design toward large gestures and forgiving hit areas, and it is a constraint worth accepting early rather than patching in late.

Flockbay builds and runs your game locally on your own machine. Its Export makes a native Windows build, an .exe. It has no export-to-phone button and does not submit anything to a store.

What it gives you is a real Godot project on your disk, which stock Godot opens. Godot exports to mobile platforms using its own tooling, and store submission is its own process involving a developer account and platform review. That work is outside this app and it is genuinely work, so plan for it rather than assume it.

If that sounds like a lot, it is worth knowing that it is the same for every serious tool. The tools that hide it usually hide it by publishing your game inside their own app, which is a different product than a game with your name on the store listing.

More on this: Make a mobile game without coding: what the no-code part covers

Free to download for Windows, macOS and Linux, and the world tools are free. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects or with Godot's own shapes, generates pictures and sound, or uses your own files. The app's Export makes a Windows build, and Godot's own export, the one that reaches a phone, is free too.

Building needs an internet connection, because the chat, asset generation and world data all come over the network. Playing the game you built does not.

More on this: Multiplatform game maker: Godot underneath, so export is not proprietary

Game work involves comparing things: this layout against that one, this value against the last one, the scene next to your reference. All of that needs screen area, and screen area is the one thing a phone cannot give you.

It also involves a lot of small precise adjustments. A mouse does that well and a finger does not, which is why on-device editors tend toward snapping grids and preset behaviours.

None of this is an argument against mobile as a destination. It is an argument about where the work happens, and every studio that ships phone games has settled the same way.

More on this: Free, no code, and still an engine rather than a toy