Quick summary
An internal tools note about building a private mode-based workflow app with timers, session continuity, device-local attachments, and export controls instead of depending on a cloud-synced task stack.
The problem
The project needed a private workflow system that could separate operating modes, keep continuity between sessions, and store notes and attachments locally without pushing sensitive data into a hosted service.
What I checked
- Mode definitions and session rules
- Focus and recovery timer requirements
- Microtask and reset-flow behavior
- Local browser storage and attachment handling
- Export, deletion, and recurring-block controls
What I changed
- Built the first release around predefined modes instead of one large undifferentiated backlog
- Added focus and recovery timers plus one active microtask per session
- Added a reset flow, last-session continuity, and timeline-style session tracking
- Stored session records in local browser storage and kept attachments in IndexedDB
- Added recurring mode blocks, private reports, export, and deletion controls
Result
The app became a practical private operating system for focused work blocks, with enough local persistence to resume sessions without adding cloud-account overhead.
Where this fix usually leads next
This kind of work usually connects back to Build useful connections between your systems, Production Debugging and Website Fixes when the same kind of problem affects your project.
What I'd watch next
- Whether local-storage schema changes need migration handling as the app grows
- Whether export formats stay useful if reports or attachment metadata expand
- Whether very large local attachments affect browser performance over time