THE DESIGN LOOP

Your engineers got faster. Your product didn't.

AI made writing code nearly free. Checking that each screen does what was asked didn't get any faster. That is where your team's time goes now.

90 seconds. It reads with the sound off.

WHERE THE TIME GOES

The code loop closes itself. The design loop waits for a person.

Write, test, fix: the verdict is objective, takes seconds and needs no screen, so an agent runs it alone, all night.

Draw, build, look, judge: is this what was asked for, and does it feel right? An agent cannot answer that alone.

ILLUSTRATIVE DIAGRAM · NOT PRODUCT UIThe code loopThe design looppass / failis it right?Judge

Every team copes in one of two ways. Both cost you.

Gloss over it

The agent's UI change looks fine in the pull request, so it ships.

WHAT IT COSTS

Users find the broken flow. Support tickets, churn, and a fix sprint you didn't plan.

Stall on it

Every UI change waits for design review: screenshots, threads, rounds.

WHAT IT COSTS

Design becomes the queue. The speed you bought with agents is spent waiting.

ILLUSTRATIVE DIAGRAM · NOT PRODUCT UIAirframethe software loop, with a UI in itRequirementDesignBuildWalkReviewLearn

THE AIRFRAME LOOP

Machines check every change against its design and requirement. People judge the rest, once.

A person reviews the design

Early, on the wireframes, before code: minutes, not a release.

The walk checks the product

It runs your real flows on a device and compares each screen to its design.

Requirements check the work

Each change is matched to the requirement it serves. Rules settle most; a model suggests the rest.

Run it by hand, or let an agent run all of it.

The whole loop is an interface. In the engagement we set review where your team wants it, product area by product area.

An agent

Any model, through MCP.

The CLI

End to end, unattended.

A person

In the app, when it matters.

Where a person steps in

PROOF

We did this on an app we'd never seen.

An open-source Android app, imported cold.

  1. Imported: its screens and flows read from the code.
  2. The walk found what was missing: no one to sign in as, nothing to start from. Fixed, then walked: 2 of 2 steps arrived.
  3. One real judgment call: a confusing screen, redesigned twice and built the same afternoon.
Airframe's Test area beside the Android emulator: the flow Todo: Open a task, started in Two open tasks, reads 2 of 2 steps arrived, and the phone shows the Task Details screen for Buy milk.
The walk, recorded 5 October 2026: Airframe on the left, the phone it drives on the right.

DESIGN LOOP ENGINEERING

We build the loop on your product. You keep it.

Two weeks · one product area · a clear decision at the end

Map

One product area: its requirements, flows and people, and the states they start in.

Engineer

Your app made walkable: real flows run automatically, on your devices.

Close the loop

Every run reports where app and design differ. People review only that.

Hand over

Your team and your agents run it. Extend it yourselves, or with us.

What you measure

Review rounds per UI change

Time from merged to 'the UI is right'

Differences found before users find them

Book a 30-minute scoping call

Bring one product area. We'll scope it on the call, or write to contact@airrostudio.com.

Want to try the loop yourself first? Airframe is free on your Mac.

Download for Mac