Four homes for data in a frontend, and the mistake of treating them as one.
State, and Why the UI Lies
Your screen is a copy of the truth, and copies drift.
Most confusing frontend bugs are one bug wearing costumes: the screen is showing a copy of data that has since changed. This course is about where state lives, which states you forgot to design, and how to lie to users honestly.
Start the first lesson0/4 lessons read
By the end you can
- Say where any given piece of state lives and who owns it
- Design the four states every piece of loaded data has
- Use optimistic updates without corrupting what users see
- Anticipate the double-submit and the lost draft
Lessons
Every piece of loaded data has four states. Most designs draw one.
Showing the result before it is confirmed, and cleaning up when you were wrong.
The double submit, the lost draft, and the validation that runs in the wrong place.