App path Data
More than one screen
An app with separate screens, where only one shows at a time and the app remembers which.
Example brief
A notes app needs a list screen, an add screen and a detail screen for reading one note in full.
An example. Use your own idea next.
Steps
- List the and what each one is for.
- Ask for each screen as a marked data-screen, and buttons that switch between them.
- Open a note from the list. Does the detail screen show that note, and can you get back?
What you will learn
- Screens
- One view of the app at a time, such as list, add or detail. They are sections on the web and views on a phone.
- Navigation state
- Remembering in the state object which screen is showing and which item is open.
A sample prompt
A notes app with three screens: a list of notes, an add screen, and a detail screen for one note. Show one screen at a time and keep track of which note is open.
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
- Save and move data Stores and portability
- Works for everyone Keyboard, focus and touch
- When things go wrong Empty and error states
- Choose where it runs Platform-neutral design
Last reviewed 2026-11-05 · version 1