What is Mistflow?
What Mistflow does, what you get at the end, and what it is not.
Mistflow builds real apps from a description. You write what you want in ordinary language, and Mistflow produces a working app: screens, sign-in, a database behind it, and a way to open it on a phone or share it as a link.
There is no configuration step, no hosting to set up, and no AI usage to pay for.
What you get
A phone app built with Mistflow is a real Expo / React Native app. It is not a website wrapped in an app shell. That matters because it decides what the app can do: camera, location, notifications, offline storage, and the native navigation people expect from an app they installed.
Alongside the phone app you get:
- A hosted preview you can open on your own phone while you are still changing things
- An installable Android build you can send to anyone
- A small web surface for your app, used for links, sign-in redirects, and store compliance
- An owner console when your app has an operator side, for example the person who manages orders
Web apps work the same way, minus the phone-specific parts.
Where the work happens
Everything happens on Mistflow's servers. You start at mistflow.ai/create, shape the idea until it looks right, and press Make it real. The build runs in the cloud, not on your machine, so you can close the tab and come back.
An AI coding editor is optional. If you already use Claude Code, Cursor, or Codex, you can connect Mistflow to it and work on the same project from there. See Use an AI editor.
Why it costs no AI tokens
You are not renting a model. The build cost is included in your plan and metered as builds, not as tokens. If your finished app calls a model at runtime, for example a coach that answers questions, that runs through Mistflow's AI gateway on a separate balance. Building the coach and people talking to the coach are billed differently and never draw from the same pool.
Key ideas
The prototype is the spec
Before anything is built, Mistflow generates a clickable prototype of the screens. You rearrange it, restyle it, add screens, and drop what you do not want. When you press Make it real, that prototype becomes the specification, so the builder does not re-ask what you already decided visually.
Nothing ships unverified
A build is not finished when the code compiles. It also has to boot, match the prototype you approved, and survive a run on a real Android emulator before you are handed a preview link. See What gets checked.
One project, more than one surface
An app usually has two audiences: the people using it and the person running it. A Mistflow project can hold both, a phone app for customers and a web console for the owner, sharing one database.
What Mistflow is not
- Not a no-code builder. It writes real code. You can take the source with you.
- Not an LLM wrapper you pay tokens for. Building is metered as builds.
- Not a way to skip the app stores. Apple and Google still control their own developer accounts, fees, and review. Mistflow can get you to a store-ready app; it cannot exempt you from the store.