Most apps begin as a design. Burrow is made for that start: it takes a design to a live app without throwing the design away.
Two ways in
Bring your frames. If your screens are already in Figma, drag them into Burrow. They arrive as real screens you can build on, not as flat pictures.
Or start here. Design directly in Burrow on a visual canvas. Either way it is one place, and the code that comes out is yours.
Figma is a trademark of its owner. We name it only to say what Burrow works with, and it does not imply any partnership.
Logic beside each screen
A screen is not an app until it does something. In Burrow, what each button does is written as short steps beside the screen. Steps read like plain sentences: when this is tapped, check that, save this, go there.
Because the steps sit next to the screen they belong to, you can read an app as a story. You do not have to hunt through a separate tool to find out what a button does.
Watch it run
Press Run and the app’s logic plays on the real screens, step by step, with real values. You see what was typed, what was saved and what came back. You can go back to an earlier moment and see how you got there.
What could go wrong
Real apps meet bad moments: no network, an empty list, a wrong password, a slow server. Burrow lets you switch these on and see what your app does. You find the awkward moment on your own computer, before a customer finds it.
Why start from the design
A design already holds a lot of decisions: the layout, the type, the colours, the order of the screens. Throwing that away to rebuild it in another tool wastes work and loses detail. Burrow starts where the design already is.
It also means designers stay in charge of the product. The person who drew the screen is the person who decides what it does, and can see it do it. Developers join the same view instead of translating a drawing into guesses.
Nothing here asks you to give up how you already work. Keep your components, your naming and your habits. Burrow reads the design as you made it, and asks you to add only the part a drawing cannot hold: what happens next.
That part is where most projects slow down, because it is where designers and developers have to meet. Putting the steps beside the screen lets that meeting happen in one place, in words both can read.
One place from first frame to store
Once the screens have their steps, the same place produces the native apps for both phones. The design is not copied into a second tool for building, and it is not handed off and forgotten. It stays the source, and the code follows it.
What is true today, and what is not
Burrow is in development. The language that holds the screens and the steps works today, and Android apps built from it build and run. The canvas, importing from Figma, and Run with its recordings are part of the Studio, which is being built next. We mark that clearly because a design tool that shows you something it cannot yet do is not worth trusting.