Tap-BPM

[Independent · 2026]

A mobile-first BPM counter for DJs who need a fast tempo check while working with vinyl, unidentified audio, or a live set.

Two Tap-BPM mobile screens showing an early reading and a stable 124 BPM result

Product brief

Tap-BPM turns a phone or browser into a focused manual tempo counter. Tap anywhere or use the Spacebar, see each beat register, and read a stable result without leaving the music.

Tap-BPM is a mobile-first browser tool for DJs who need a quick tempo reference while working with vinyl, external audio, or a track that is not already analyzed. The product opens directly to one task: tap with the beat and read the estimate. It is designed for touch, one-handed use, large targets, immediate feedback, and low-light readability.

Try Tap-BPM ↗

The solution

01  /  04 1

A tap surface instead of a tap button

People change grip and move between thumb and index-finger input, so precision is the wrong requirement for primary input. The interface treats most of the screen as the tap target, reducing the need to aim while a DJ is working. Touch leads on mobile, click provides the desktop equivalent, and Spacebar offers a fast keyboard path.

Orange theme mobile frames showing the inactive and active full-screen tap target
02  /  04 2

A visible rhythm trail

Each input produces an immediate pulse and advances the timing markers. The newest mark arrives in orange, recent beats remain visible, and the tail fades toward gray so history supports the rhythm without competing with the next tap.

Timing tap feedback marks progressing from an active orange ring to a quiet gray trail
03  /  04 3

Confidence without a moving target

Early BPM numbers can appear more certain than the input supports, so the BPM stays anchored while the surrounding record form and status language communicate activity. Measuring, stabilizing, and stable states make an early estimate feel different from a settled result: an initial estimate after three taps, a stable reading after six to eight consistent taps. Reduced motion preserves the state change without the larger reaction.

Dark theme mobile screens showing measuring and stable Tap-BPM states
04  /  04 4

Motion studies: testing the range of feedback

Focused motion studies explored how much energy the feedback could carry before it competed with the reading, from a literal timing sequence to intentionally exaggerated deformation. These are exploratory studies, not evidence of validated DJ preference.

Animated Tap-BPM timing study with an orange tap ring advancing across eight timing positions

Tap. Read.
Return to
the music.

By the numbers

Dark theme mobile frames showing Tap-BPM tap feedback

1

full-screen primary tap surface

3

input paths: touch, pointer, and Spacebar

3 → 6 to 8

taps from first estimate to a stable reading, proposed for testing

My role

I set the product direction, reviewed the category, defined the interaction and motion behavior, designed the responsive interface and identity, and built the working browser prototype. V1 includes touch, click, and Spacebar input; live BPM and tap history; measuring and stable states; reset; half and double tempo; themes; and reduced-motion behavior.

Role

Creator and Product Designer

Timeframe

2026

Disciplines

Product Design, Interaction Design, Creative Tools

Current state

The result is a working responsive browser prototype that establishes the complete V1 interaction loop without claiming adoption or usability outcomes that have not been measured.

Working prototype

Touch, click, and Spacebar input in one responsive browser app

Feedback system

Live BPM, tap timing, reset, themes, and reduced motion behavior

Platform

Responsive web app

Problems & decisions

Research and competitive review shaped a full-surface tap model, progressive confidence states, concise motion feedback, and a responsive implementation for phone and desktop.

Basic BPM counters already solve the calculation. The small competitor sample I reviewed provided limited tap feedback, made measurement progress difficult to understand, and generally behaved like desktop calculators rather than responsive music tools.

A DJ may need an immediate tempo check while attention stays on the record, room, and mix. Small targets, setup steps, and ambiguous early readings add work at exactly the wrong moment.

Should interaction center on a conventional tap button, or should the whole experience behave as the instrument? I let the screen, pointer, and Spacebar share one primary tap action, keeping the BPM fixed at the center while expressive feedback moves around it. The tradeoff: the full-surface model needs careful event handling so theme, reset, half, and double controls stay distinct from tempo input, and the proposed confidence thresholds still require direct testing.

The early evidence combines a small competitor review, general mobile interaction research, and product prototyping. Direct observational research with DJs, a validated confidence threshold, and adoption or usability metrics remain outside the current evidence.

Making a utility feel alive depends on precise, brief feedback rather than motion volume. The BPM stays still while feedback happens around it. Direct usability testing with DJs is the next step to validate hand posture, booth legibility, haptic value, and confidence thresholds.