Notebook Entry 009

Architecture

localStorage Is a Filing Cabinet Bolted to One Desk

April 8, 2026

What breaks when a single-device tool has to work across devices?

What happened

Lane Command v1 used browser localStorage for all task data. Worked great — until Amanda wanted to use it on her phone too. localStorage is device-specific and browser-specific. Clear your browser data, lose your tasks. Use a different device, start from zero.

Decision made

Replace localStorage with Firebase Firestore (cloud database) + Google Authentication (so the system knows who you are on any device). Same app, same UI — different storage layer.

Why it matters

This is the exact gap Amanda talks about in her newsletter. The technology decision (localStorage vs cloud database) isn't a coding decision — it's an implementation decision. Who's using this? On what devices? What happens when they clear their cache? Those are operations questions, not engineering questions.

The lesson

The first version of any tool reveals the requirements the spec missed. Build v1 fast, use it, and let real usage tell you what needs to change. The localStorage-to-Firestore migration happened in one session because the app was already built and working — the upgrade was surgical, not a rebuild.

One implementation insight every other Tuesday.

What actually works when you ship AI in real organizations. Nothing you could get from a press release.