Learning to build for offline
A small browser-storage experiment, and the questions it raised about ownership, backups, and trust.
The question
What would a useful tool look like if it did not need an account? This fictional learning exercise starts with a note saved in browser storage.
The first lesson
Saving locally is only part of the story. The interface must explain where information lives and how to export it. A person should not have to understand browser internals to keep their work safe.
A better next step
Build a complete loop: create a note, close the page, reopen it, export it, and restore it. The learning comes from completing the path, not simply making a successful write.
Still exploring
How should a small tool explain storage limits? When does synchronization become worth the extra complexity? Those questions are more interesting now that there is a simple prototype to think with.