App path Quality
When things go wrong
An app that stays calm when a list is empty, input is wrong or imported data is damaged.
Example brief
A planner where importing a broken file must show a clear message and leave the existing list untouched.
An example. Use your own idea next.
Steps
- List three things that can go wrong, such as empty input, an empty list and a bad import.
- Ask for a clear message for each, shown in a status or alert element.
- Paste broken text into Import. Is the old list still there?
What you will learn
- Empty state
- What a screen shows when there is nothing yet. It should say what the screen is for and how to start.
- Error state
- What the app shows when something fails. It names the problem and what to do, and never loses the person's data.
- Defensive input
- Treating everything that comes in, typed or imported, as possibly wrong and checking it before use.
A sample prompt
A task planner. Show a friendly message when the list is empty. Reject empty names with a message. If imported data is not valid JSON, show an error and keep the current tasks.
Write yours first, then compare.
To complete it
Pass all 9 checks on one version, then accept.
More in the app path
- Your first screen Say what the app does
- Keep track of things State and render
- Forms people can finish Labels and validation
- More than one screen Screens and navigation
- Save and move data Stores and portability
- Works for everyone Keyboard, focus and touch
- Choose where it runs Platform-neutral design
Last reviewed 2026-11-05 · version 1