A utility should disappear into the task.
The Tally Counter project was built as a focused browser utility rather than a feature-heavy dashboard. The central interaction needed to be immediate: see the current number, change it, and trust that the state will still be there later.
That led to persistent data, independent counters, chronological logs, and small supporting tools without introducing a framework.
Simple on the surface. Reliable underneath.
Persistent state
Store counter data and history locally in structured JSON.
Independent records
Allow multiple counters without cross-contamination.
Readable history
Keep action logs through resets for auditability.
Accessible controls
Use semantic controls, visible focus, keyboard behavior, and responsive layouts.
Vanilla technologies, deliberate structure.
The app separates storage, rendering, interaction, and utilities. Event delegation reduces duplicated listeners, while defensive localStorage parsing prevents malformed stored data from breaking the application.
The interface communicates state before decoration. Every border, label, number, and accent has a job.
Core system.
- Unlimited independent tally records.
- Increase, decrease, reset, rename, custom-number entry, and deletion.
- Chronological action logs with previous value, change, and resulting value.
- Local persistence with defensive validation.
- Responsive technical interface and accessible interaction patterns.
- Stopwatch, timer, and expression-based calculator utilities.
Small utilities still deserve systems thinking.
Simplicity is not the absence of engineering. Persistent state, recovery behavior, keyboard interaction, responsive layout, and clear feedback all need decisions even when the visible product is just a counter.