Would you voluntarily spend another five hours on this kind of problem? Why?
Mobile App Development · 90–120 min
Make a reading list survive a restart
Feel state, persistence and interruptions—not just drawing a screen.
Start the experiment01 · Setup
What you need
- Basic programming and one mobile starter app already running on your chosen emulator/device. Setup time is separate; use the linked platform guide first.
You may stop when the timebox ends. An incomplete result is still useful evidence.
02 · Task
The work sequence
- 01
Create a list with a title field, Add action and a clear empty state. Keep it local; no login or backend.
- 02
Save entries in local storage supported by your stack, then close and reopen the app.
- 03
Test duplicate taps, empty titles, larger text and switching to another app. Record one failure.
- 04
Fix the failure, add a small test for the state logic and explain where data lives. If time runs out, document the reproduction and continue later.
03 · Pay attention
Watch your reaction, not only the output
- Was preserving a user's work more interesting than adding a second screen?
- Can you explain the difference between temporary UI state and persisted data?
Plot twist
Difficulty does not mean the career is a bad fit. The useful question is whether curiosity returned after the difficulty.
04 · Reflect
Three honest questions
Which part gave you energy, and which part drained it?
What evidence—not a salary video—would you gather before choosing this path?
This site does not save your answers. Put them in your own notebook if useful.
05 · Where to go next