App path Data
Save and move data
An app whose data goes through one Store, so it can be saved, exported, and moved to a database later.
Example brief
A habit tracker needs to keep its data between visits and let a person take it to another device.
An example. Use your own idea next.
Steps
- Ask for a object with load and save, and a block for names and keys.
- Add Export and Import buttons that use JSON.
- Export, change something, then import. Did the data come back exactly?
What you will learn
- Store
- A small piece of code that is the only place data is read or written. Screens ask it; they never touch storage.
- Portable data
- Data in a plain format such as JSON that any platform can read, so it can move with the person.
- Config
- One block holding names, keys and addresses, so moving to a new platform means editing one place.
A sample prompt
A habit tracker. All data goes through a store object with load and save, settings live in one CONFIG block, and there are Export and Import buttons that use JSON. Show a message when import fails.
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
- 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