← Back to projects
CASE STUDY / PRJ-001 / WEB APP

Tally Counter
Web App.

A fast browser-based counting utility designed around persistent data, multiple independent tallies, readable logs, and keyboard-friendly controls.

ROLEDESIGN / DEVELOPMENT
STACKHTML / CSS / JS
TYPEUTILITY WEB APP
STATUSCOMPLETE
COUNTER / ACTIVE SESSIONLOCAL STORAGE
042
−+LOG
01 / OVERVIEW

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.

02 / GOALS

Simple on the surface. Reliable underneath.

01

Persistent state

Store counter data and history locally in structured JSON.

02

Independent records

Allow multiple counters without cross-contamination.

03

Readable history

Keep action logs through resets for auditability.

04

Accessible controls

Use semantic controls, visible focus, keyboard behavior, and responsive layouts.

03 / APPROACH

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.

DESIGN PRINCIPLE

The interface communicates state before decoration. Every border, label, number, and accent has a job.

04 / FEATURES

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.
05 / LESSONS

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.

← All projectsNext project →