Understand / lifespan Public design record

Product history, starting here

What the app became,
one revision at a time.

A living record of Understand, an offline listening companion for difficult text. Start with the current design checkpoint. Older chapters will be added without rewriting this one.

Current chapter · Revision 05

The first preserved chapter

One place to see what changed, what is fixed, and what comes next.

The current package turns the redesign into something you can walk through. Library owns the durable root. Reader owns the listening surface. The matter orb owns play and pause. Voice preview stays inside the Voice sheet. The heard sentence gets the strongest contrast.

Five specialist reviews fed this revision. The package covers 78 canonical states and leaves eight owner decisions visible instead of burying them in a report.

78canonical states
08owner decisions
05specialist reviews
Saved here: the public snapshot includes the current design contract, review package, visual source, and supporting evidence.
The record

Keep the chapters intact

Each chapter gets its own boundary. A later revision can disagree with an earlier one without erasing it.

Now · Revision 05Current

The design package is ready to decide.

Five reviews became one package. The current record holds 78 states, three locked owner anchors, and eight decisions that still shape the Flutter port.

Open this chapter →
Earlier chaptersTo be added

The earlier versions stay untouched.

Older explorations and prior state packages will come here later. They are not rewritten into the current story, and they are not being presented as release history yet.

Supporting material

Read the decisions behind the screen

The interactive review is the front door. These documents carry the detail.

Five review lenses
Information architecture
Open the current IA. Library, Reader, sheets, recovery, and ownership are named there.
Visual source
Open the pinned Flow source. It is the reference used to compare the package.
What happens next
Read the replacement plan. The port follows owner decisions and a replay of the user story on device.