Notes

2 min read

Watch it run: seeing your app’s logic before it ships

Run the app’s logic on the real screens, step by step, with real values, and look back through any moment.

Most design tools show you how an app looks. Few show you how it behaves. Burrow is made to show both, because the second is where apps go wrong.

The problem with logic

A screen is easy to see. A rule such as “only people over eighteen see this offer, unless they have already claimed it” is not. It lives in someone’s head, or in code that few people read. When it is wrong, you find out from a customer.

Run, on the real screens

In Burrow you press Run, and the logic plays on the same screens you designed. You tap the button and see the steps happen one after another: what was read, what was decided, what was saved, where the app went next.

You see real values at each step, not a diagram of values. If a total is wrong, you see the number that made it wrong.

Look back

Runs can be recorded. You can scrub back through a recording and stop at any moment, to see the state of the app at that point. When something odd happens, you do not have to reproduce it. You can look at what already happened.

Every change is checked

Watching is one half. The other half is checking. Before an app can ship, Burrow checks every change and tells you in plain words if something does not add up: a missing screen, a value used the wrong way, a step that can never be reached.

Together the two give a team a shared view. A designer, a product manager and a developer can look at the same run and agree on what the app does.

Why it matters for design

  • Earlier. Problems appear while you design, not after release.
  • Together. One run is something everyone can see, not something one person explains.
  • Safer. A change that breaks something shows up before it ships.

A shared view

Design reviews are often an argument about what someone meant. A run settles it. Instead of reading a specification, the team watches the app do the thing, and can stop at the step where they disagree.

It also changes how a designer works. You can try an idea in minutes, see it run and throw it away if it is wrong. The cost of a bad idea falls, and the number of good ones you can try goes up.

Not a replacement for tests

Watching is not the same as testing, and we do not pretend it is. Burrow also builds in checks and tests that run again and again without you. Run is for understanding and for finding the surprise. Tests are for making sure the surprise stays gone.

What is true today

Burrow is in development. The language the steps are written in works today, and every change to it is checked. Run, with its recordings and the real-value view, belongs to the Studio, which is being built after the language and the app library. When it lands, the build notes will show it running.

Read next

Connects to anything: your backend stays yours

Read it