Notes

2 min read

Your code, yours to keep

Burrow writes standard projects you can open in Xcode and Android Studio. Nothing to rent to keep your app alive.

Think about the day you stop using a tool. For many builders, that is the day the app stops: the app lives on their servers, in their format, and leaving means starting again. We think that is the wrong deal for a product people depend on.

A standard project

Burrow writes a normal project for each phone. For iPhone, a project you open in Xcode, written in Swift with SwiftUI. For Android, a project you open in Android Studio, written in Kotlin with Jetpack Compose.

These are the same tools and the same kinds of files that any developer uses. Another developer can pick them up without knowing Burrow. A new hire can read them. A security reviewer can audit them.

Nothing to rent

Your app does not run on Burrow’s servers. It does not call home to check a licence. There is no monthly fee to keep the app alive, because the app does not depend on us to run.

Your backend is yours too. If your app talks to a server or a database, that connection is between your app and your service. And your AI key is yours, so no part of the chain is something you rent from us.

Why this matters to a team

  • Hiring. You can bring in developers at any time, and they work in the tools they know.
  • Review. Your code can be read, tested and approved by your own people.
  • Exit. If you ever want to leave Burrow, you take a working project with you.
  • Longevity. The app outlives any tool, including this one.

Both ways

Owning the code does not mean giving up the design. Burrow is built so that you can edit the code and keep editing visually; the two stay in step. You choose how to work, and you can change how you work whenever you like.

What “yours” means in practice

You can store the project in your own repository, with your own history and your own reviews. You can build it on your own computer or on your own build servers. You can submit it to the stores under your own developer accounts, so the app is listed under your name and your company, not ours.

If you choose to hand the project to a developer, they receive a normal codebase with ordinary tools and ordinary files. They are not asked to learn a new system, and they are not asked to ask us for permission.

A promise that shapes the build

This is not a feature added at the end. It is a rule we build by. Every part of Burrow is made so that what comes out is something you can hold, read and keep. If a feature could only work by tying your app to us, we would not build it that way.

What is true today

Burrow is in development. Today the language works and Burrow writes Android projects that build and run on a phone emulator. The iPhone project is being built: the Swift is checked on a PC now, and the first runs on a real Mac come next. The promise of a standard project you own is the design we hold every part of the build to.

Read next

From Figma to a live app

Read it