No-code mobile game maker: check the ceiling before you commit

What happens when I want something that is not on the list? For a menu-driven tool the honest answer is that you cannot have it, and you will change your game to fit what the tool offers. That happens quietly and it happens to almost everyone who sticks with a project past the first fortnight.

For a tool where actual code is written on your behalf, the answer is that you ask for it and then iterate until it works. It might take a few passes. There is no category that is unavailable.

Flockbay is the second sort. Flockbay writes GDScript inside your Godot project. You never open it, and you are never told a thing cannot be done because it is not in the catalogue.

More on this: Make a game without coding, and without a ceiling

Flockbay is a desktop app for Windows. Not a phone app, not a browser tool. You install it and build on a computer.

The game runs locally on the copy of open-source Godot bundled with the app. Nothing streams and nothing renders elsewhere.

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

It covers the entire game: controls, touch input, UI behaviour, progression, saving, scoring, unlocks. All of it described in plain language and written for you.

It also covers the world, which you build by hand rather than by writing anything. A new project asks 2D or 3D before it will create anything. Flat, which is what most phone games are, means ground you drag into place a cell at a time and sprites put at the position, turn and size you chose. 3D means terrain, water, weather, structures and props. Either way it is a viewport and a mouse and not a line of code.

It does not cover getting the finished thing onto a phone. Your project is a standard Godot project, and mobile export plus a store submission is separate work with its own accounts, signing and review. No-code removes the programming barrier; it does not remove the platform.

More on this: You build on a computer, even when the game is for a phone

If the plan involves ads, in-app purchases and retention mechanics, be aware that those bring their own SDKs and platform requirements, and they are the least interesting part of any mobile project to build.

There are toolchains built specifically around that model and they will get you there faster. What Flockbay is good for is the game itself — a thing with a design you care about, built by you, in a project you own.

More on this: Make a mobile game with AI: build it on a desktop, honestly

The download is free and so is the builder — tile ground and sprite placement in a 2D project, landscape, water, weather and time of day in a 3D one, and cameras, behaviour and your own assets in both. Flockbay is free on your own AI: 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.

No per-seat pricing and no team tier, and Flockbay takes no share of your sales. It is a desktop app for one person, and it is free.

More on this: Making a Steam game with AI: what the platform actually requires

While a project is going well, the format it is stored in seems like a technicality. It stops being a technicality the moment you need something the tool does not offer, or the tool changes, or you want someone else to look at it.

A standard Godot project on your own disk can be opened by anyone who knows Godot, kept in version control, backed up, and carried anywhere. It does not depend on this app continuing to exist.

That is worth thinking about at the start rather than at the end, because it is the one decision that cannot be reversed once a project has months of work in it.