A first version of an app is the easy part. The hard part comes later: the product has two hundred screens, six people changing it, and a store that announces new rules every year. Most app builders are not made for that stage. Burrow is.
Any number of screens, kept in parts
A large app is not one big pile. Burrow keeps an app in modules, small parts with clear edges, such as sign-in, search or checkout. A part can be changed without shaking the rest, and a team can share the work without stepping on each other.
The design is that the thousandth screen is as smooth to work on as the tenth. That is a goal we build toward, and we say so as one.
Every change is checked
In a growing app, the dangerous change is the small one that quietly breaks something far away. So Burrow checks every change before it can ship. If a button points at a screen that no longer exists, or a piece of data is used the wrong way, Burrow tells you in plain words, before anyone sees it.
We do not promise an app with no bugs. We promise that a whole family of mistakes is caught before release, every time.
Yearly updates, handled
Apple and Google change their rules and tools every year. Apps that ignore this stop being accepted by the stores. Burrow follows the yearly changes, so that the code it writes keeps meeting the stores’ requirements, and updating is a routine step, not a rescue.
Old versions keep working
Not everyone updates the moment you release. Some people keep an old version for months. Burrow is built so that an old version of your app keeps working for them, including the data it saved, while newer versions move ahead.
An honest count
“Built for any app” is easy to say. So we keep a written list of what real apps and the two programming languages need, taken from the official Android, iOS, Kotlin and Swift documentation: 228 things an app does on a phone and 286 features of the languages, 514 lines in all. A line is ticked only when it runs, on both phones, with a test or an example to show it.
On the last count, 208 of the 514 were native, 116 were partly there and 190 were not built yet. That list is the measure we hold ourselves to, and the build notes will keep reporting it.
A team can work on it
Growth is also about people. A product with one author becomes a product with many. Because Burrow keeps the design and the steps in a readable form, a newcomer can open a part and understand it. Because every change is checked, a newcomer’s change is safer to accept.
A large app is also a long conversation between designers, product managers and developers. When all three can read the same screens, the same steps and the same run, there is less to explain and less to misunderstand.
Why we say this plainly
Most builders are made for the first version. We think a product’s real test is the fifth. Saying so is part of the promise: we would rather be known for an app that is still working, and still easy to change, in three years, than for how quickly the first screen appeared.
What is true today
Burrow is in development. The language works, and Android apps built from it build and run. The parts described here, from modules to yearly updates, are the direction of the build, and each one will be marked in the notes as it lands.