# A walking app trades a feature tour for a useful story

Companion to /learn/conversion/screenshot-strategy/

## Outcome
Brief a screenshot sequence in which every frame answers a useful buying question.

Fictional example, not a client result.

## Scenario
NearWalk is a fictional app for short walks. Its current sequence shows a splash screen, a settings menu and a dense map. The product actually helps someone choose a suitable walk for the time they have. The existing screenshots show interfaces without explaining that decision.

## Reasoning
Write the visitor’s questions before opening a design tool: is there something near me, can I judge whether it fits my time, and do I understand where to start? Assign one question to each frame. Select real supported product screens as evidence and write captions that connect the screen to the question. A sequence should remain understandable even if someone sees only its opening.

## Action
Draft three frames: a nearby option, the route details that help a person choose, and the starting instructions. Test the small-size readability and ask a relevant reviewer to describe the app without coaching. If the reviewer invents a feature or misses the central use case, revise the message before adding visual polish. Treat the concept as a hypothesis until appropriate performance evidence exists.

## Trap to avoid
Do not squeeze every feature into the opening image. A visitor needs a coherent reason to continue, not a miniature specification sheet. Prioritise the product’s relevant promise and use later frames to supply evidence and reassurance.

## Advanced considerations
Create alternative arguments before cosmetic variants. One concept might lead with a completed outcome; another with the ease of the first action. Document the mechanism each is intended to improve. If you test only shades of the same background, the result may tell you little about the more important uncertainty in the listing’s message.

## Exercise
The designer wants to open with an attractive dashboard because it has more colour. What should the brief use to decide?

## Suggested answer
Compare which frame best explains the priority user outcome at realistic viewing size. Visual appeal matters, but it should serve that job. If the dashboard demonstrates the outcome clearly it may work; if it only displays interface complexity, another screen may be stronger.

## Your worksheet

### Audience and arrival context
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Question answered by each frame
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Caption and product evidence
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### What must remain legible at small size
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Claims and localization constraints
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Comprehension review and test hypothesis
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## A production-ready brief structure for NearWalk
These are illustrative captions and asset requirements for the fictional walking app. They extend the visual storyboard into a handoff a designer can act on. Product screenshots and route details must be real and verified before production.

Fictional creative handoff. Captions are directions to validate, not proven winning copy.
Frame and caption direction | Required product evidence | Acceptance check
1 — Find a walk for this afternoon | Nearby route options with meaningful time context | A new viewer recognises local walking, not expedition planning
2 — Choose a route that suits your time | Route detail screen with supported duration information | Key details remain readable without zooming
3 — Know where to begin | Actual start-point instructions or supported navigation workflow | No implication of unavailable live navigation
Variant brief — Lead with the starting workflow | Same product truth, different opening argument | Document the changed question; avoid unrelated cosmetic changes

### Give the designer constraints as well as captions
Supply the audience, arrival context, approved product screens and claims to avoid. State what must be visible in each frame and what can be simplified for clarity without altering the product truth. Include device and localization deliverables after confirming the current store specifications. A caption list without these details leaves important decisions to guesswork.

### Run a comprehension review before polishing
Show the sequence at a realistic viewing size to someone unfamiliar with the app. Ask what the app does, whom it serves and what they expect after installation. Avoid telling them the intended answer first. Note misunderstandings separately from aesthetic preferences. This review can expose clarity problems; it does not measure a conversion uplift.

### Define the handoff and the test separately
Creative approval checks product accuracy, readability and message coherence. Experiment approval checks the audience, supported setup, primary measure and interpretation plan. Passing the first does not establish that the design performs better. Keep both decisions documented, and preserve the control assets so the team can reconstruct the actual comparison.

## Continue reading
- /learn/conversion/first-screenshots/
- /learn/conversion/screenshot-readability/
- /learn/conversion/ab-test-hypotheses/