Understand — First Run

A first-run flow for Understand should feel like entry into a real reading and listening session, not a small playable demo detached from the product.

Current Understand library wireframe with continue listening, starter books, and own-text entry. — Current direction: a library surface that immediately looks like the beginning of a real reading-and-listening product.

The question

Understand is trying to help someone stay with a difficult, older, or distant text they might otherwise lose. The design question here was how quickly first-run could get a new person into that feeling without shrinking the product into a sample-sized trick.

The underlying product is built around the listening session. That meant the opening could not just prove that audio starts. It had to suggest a real path into a text the person could continue with.

Why this mattered

If the first interaction looks like a self-contained sample, the app feels smaller than it really is. If it feels like the beginning of a listening session inside a larger work, the product promise becomes much clearer.

What first-run needed to prove

Not just that audio can start, but that the app can make a difficult text feel easier to stay with and worth continuing.

Why the library mattered

Cold-open users should enter through a real library of whole works, because the product should teach continuity into real reading and listening rather than a disposable sample.

Current proof

The strongest current direction is not one isolated screen. It is the first-run handoff: a library surface that feels like a real listening product, then a reader surface that makes it obvious the person is inside an actual book rather than a disposable sample.

Understand library wireframe with continue listening, starter books, and direct text/file entry. — **Entry point — Library first, not sample card first.** The opening now gives someone a book to continue, whole works to start, and immediate ways to bring their own text.

Understand reader wireframe with passage text, playback controls, and retelling versus original controls. — **Destination — Reader view that feels like the beginning of a session.** Once inside the text, the book context stays visible and the listening controls stay close.

What went wrong before

The earlier version proved playback, but it taught the wrong rhythm. Someone could tap, hear something, and understand the mechanic, but the experience still felt stop-start. It made the app read more like a novelty proof than an environment for sustained listening.

Earlier V1 Understand wireframe with a small playable sample card. — **V1 — Tiny playable example.** Quick proof of audio, but too much like a little sample instead of the start of a relationship with the text.

V2 Understand wireframe with a fuller preloaded passage. — **V2 — Fuller passage state.** More text context and a clearer sense of passage, but still a bridge artifact rather than the app’s actual next shape.

What changed

The design got better once the product stopped centering the sample and started centering the session. That shift changed the whole structure: the library became the entry point, the text view became the real destination, and the opening interaction started to imply a whole work the person could continue through.

Library → Play → text view → continue.

That is the core move this study is defending. It also exposed a deeper requirement: the opening object had to generalize to real passages, documents, and books rather than only looking good as a compressed sample.

Process shift

Earlier design work happened directly inside Codex, which meant the same tool was jumping across visual design, structure, information architecture, and UX thinking at once. The process then shifted into Open Design — the open-source design tool — because it fit the current job better and felt closer to how I had done UX work in the past: slower, clearer, and more focused on IA, big-picture structure, and layout.

What Codex was doing before

Codex was helping directly with visual direction as well as structure, IA, and UX decisions. That made it useful for exploration, but it also blurred the boundary between design thinking and artifact-making.

Why Open Design became the focus

Open Design gave the wireframe work a more natural place to live. It matched the current phase better: less attention on old prototype routes, more attention on the wireframes, the product model, and the structural questions that still need resolving.