Module 16 of 18 · Run the studio

Flows and approvals

The steps your product goes through, written down as data rather than code: what happens, in which order, and where a gate stops for a person. Anything that spends money, publishes or deletes raises an approval request with the price on the button, and your yes is tied to that exact call, once.

You say
“Every release: build, test, screenshots, then ask me before TestFlight.”
Neo · Flows and approvals
Release flow
0/3
Build
Tests
Screenshots

A recreated panel in the style of the app: how a turn in this module goes, built only from what the module really does.

What you can do with it

3 things you can do with it.

BuildTestShip

Steps as data

A process you can read and change, not code you have to maintain.

Tests pass
Then screenshots

Gates

A step only runs when the one before it passed.

Upload to TestFlight
Waits for your yes
Approve

Approval requests

Spend, publish or delete stops and asks, with the price on the button.

You say…

Plain words in the one chat.

“Every release: build, test, screenshots, then ask me before TestFlight.”
“Add a gate: the tests must pass before the screenshots.”
“Show me what is waiting for my approval.”

You never pick the module. Neo reads the request, picks Flows and approvals, and says why.

What you get at the end

What you hold when it is done.

  • A process that runs the same way every time
  • Approval requests in one place
  • A record of what was approved, and when

Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.