New Recipes, Bakery Open

How does an app change without ever closing?

This film needs JavaScript and WebGL.

Software is never finished. Every week, Doña Carmen's app gets a new button, a fix, a new price. The trick is changing it while people are still ordering.
The app's recipe lives in one shared book with a perfect memory. Every change, who made it, and why. That book is called the repository.
To try a new recipe, a cook copies the book onto a side track, called a branch, and experiments there. Meanwhile the main book keeps feeding customers.
When it's ready, the cook asks to fold it back into the main book. Other cooks taste it, and comment, first.
Right away, a machine bakes it and checks everything. Does it build? Does every old recipe still work? Is anything unsafe? If anything fails, the line stops.
Fixed, and green across the board. Now the change joins the main book.
But it doesn't go straight to customers. First, the test kitchen. Then a practice kitchen that looks exactly like the real one. Then, the bakery.
Even then, carefully. The new recipe goes to a few customers first. If they're happy, everyone gets it.
And if something goes wrong, one button brings yesterday's recipe back in seconds.
A counter, a kitchen, a pantry and a helper. A window with rules. A journey through glass. A building full of computers. And a recipe that keeps getting better. That's software. Now you've seen inside.