People ask us how Burrow differs from the other ways to make an app. The honest answer starts with what those ways do well, because each of them does something well.
Three kinds of tools
AI-first builders start from a sentence. You describe an app and get one back. That is fast, and it is a good way to see an idea. The cost is control: the app is not one you designed, and changing a small thing can change a large one.
Visual builders let you drag parts onto a page and connect them. They are friendly and quick to launch. Most of them stop at launch. The app lives inside the builder, runs on the builder’s engine, and is hard to take with you.
Cross-platform toolkits let a developer write one program for two phones. They save effort, but the result often feels at home on neither phone, and they ask you to write code.
Where Burrow differs
- Designers first. Burrow is a design studio. You design the screens and what they do. You do not start from a prompt, and you do not need to be a developer.
- Native on both phones. Real SwiftUI on iPhone and real Jetpack Compose on Android. Not a web view, not a look-alike.
- Your code. The result is a standard project you can open in the usual tools. Nothing to rent to keep the app alive.
- Built for after launch. Apps grow: more screens, more people, new store rules every year. Burrow is built for that long life, not only for the first week.
- Your key. AI is a tool you call on, with the model and the key you choose. You pay the provider directly.
- Your backend. If you already run a server or a database, keep it. Burrow connects to it.
What this means in practice
Most builders are made to get an app out overnight. That is a fine goal, and it is not ours. We care about the app in its third year, with hundreds of screens, a team of people working on it, and a store that changes its rules.
So the choices we make are different. Every change is checked before it ships. The app is split into parts that stay small. Old versions of your app keep working for people who never update. None of this is exciting in a demo. All of it matters on the day your product has real users.
Who each one suits
If you want to see an idea in an afternoon, an AI-first builder may be exactly right. If you need a simple app for a small event, a visual builder may be enough. If your team already writes code and wants to share it between phones, a cross-platform toolkit may fit.
Burrow is for the person in the middle of those: someone who designs a product, wants it native on both phones, and expects to keep working on it for years. That person usually wants control over the design, ownership of the code and a clear view of what the app does. Those are the things we put first.
It is also why we do not sell speed as the main point. Speed is welcome, and you will have it, because you design visually. But an app that is fast to make and hard to keep is a bad trade for a product you depend on.
What is true today
Burrow is in development. Today the language works, and Android apps built from it build and run. Much of the rest is being built, in a set order, and the build notes say where each part stands. We would rather you hear “not built yet” from us than find out later.
If you design products and want them native on both phones, without giving up your code, join the waitlist and follow the notes.