Skip to content

The finish review

What is checked on every built screen before it ships, which convention wins and what becomes of a finding.

Every built screen is reviewed for its details and its motion before it ships, by someone who did not build it. Khaeli's product pipeline holds a gate on the result: a screen ships only when its interface and its motion are both approved for its files as they stand.

What a reviewer checks

Harbour studio
  • Home
  • Invoices
  • Customers
  • Payments
  • Settings

Invoices

5 invoices, £4,320.00 outstanding

Invoice CustomerStatusAmount
INV-2051Brightwater DentalOverdue£1,280.00
INV-2050Kestrel Print CoSent£640.00
INV-2049Oakline JoinerySent£2,400.00
INV-2048Pennant CyclesPaid£915.00
INV-2047Fernhill BakeryDraft£350.00
  1. Words

    Sentence case, a verb on every button, a count with its noun.

  2. Keyboard

    Every control takes focus, shows its ring and has a name.

  3. Rows

    Rows part on a hairline, with no stripes and no column rules.

  4. Colour

    A status is a tint and a word, never colour alone.

  5. Type

    One body role in two weights, the title one role above it.

  6. Motion

    A hovered row changes colour and nothing else moves.

The reviewer reads the screen in a browser, in every state it has, at each width and in each theme the product ships. The Budgets are not on the list, because a test has already counted them.

Which convention wins

1
The foundationNever a finding
2
The product's design.md
3
House Taste

Where two conventions differ, the earlier one holds, so a value the foundation fixes is never a finding. A product departs from a House Taste rule only with the reason written in its design.md.

What a finding becomes

A hand-typed ease on a row's hover
Fixed with a token
A flaw inside the menu component
Reported upstream
A press scale unlike a skill's number
Not a finding
How the dialog feels on a phone
Left for the owner
Totals sit at the foot of every table
Written into design.md

A finding in the screen's own files is fixed there, with a token wherever it names a value, and the screen is reviewed again. A finding in a Registry component is reported once and never holds the screen back.

The skills behind it

The interface is reviewed with Jakub Krehel's better-interface: accessibility, layout, writing, typography, colour and UI on one screen. The motion is reviewed with Emil Kowalski's remove-animations and review-animations: what stays, by the table of verdicts, then the code that is left.