← Back to work

Case file 03 · App · macOS + Web

Tapit

A Mac menu bar app that plays mechanical keyboard sounds as you type and goes quiet by itself on a call, and Tapit Daily, the free typing game that grew out of it: five short rounds a day on the web, the same for everyone.

Year
2026
Role
Solo: design, build and sound packs
Read
5 min
~4.6 msKey to sound, target under 10
21Sound packs
120Daily challenge themes
27Badges

Context

This is the story of Tapit, from a Mac app to the daily game that grew out of it. Tapit started as a Mac menu bar app that plays a mechanical keyboard sound every time you press a key. It's a small niche with a lot of apps in it already. Klack sells for $4.99, Thock is free and open source, and Haptyk reads the MacBook's motion sensor to tell how hard you hit each key.

I started it because of an app I'd found called Mechvibes, which plays a keyboard sound as you type. The idea was great, but the interface was horrible and it didn't live in the menu bar. My first thought was that I could probably build that myself. It's now two things: the app, which works but isn't released yet, and Tapit Daily, a free typing game on the web that came out of trying to market it.

The problem

With that many apps around, Tapit had to do something the others don't. Reading what people complained about, one thing kept coming up: you have to remember to mute the app before a call, or everyone hears you typing. Other complaints were a delay on the first key, sounds that repeat like a machine, and no way to set the volume apart from the Mac's.

It also has to be fast. If the click lands after the key, it feels wrong straight away. The target I set was under 10 milliseconds from key press to sound.

What I built

A native app in Swift. It hears each key press, with the Mac's Input Monitoring permission, and plays it through an audio engine that's kept warm, so even the first key is instant. Over about 300 keystrokes on my MacBook Air, key to sound came out at about 4.6 milliseconds.

When any app starts using the microphone, Tapit goes silent or turns itself down, names the app that's using it, and Tappy, the keycap mascot in the menu bar, turns orange until the call ends. I tested it on a real WhatsApp call.

There are 21 sound packs: two generated in code, six made from free (CC0) recordings, and thirteen built from kbsim, an open-source keyboard simulator with separate sounds for each row, the space bar, enter and key release. Around that sit a Stats page with 27 badges, a Playground for typing races, and a Daily challenge with 120 themes.

Tapit Daily is plain HTML, CSS and JavaScript with no build step, plus a few Vercel functions and a Redis store that keeps anonymous scores and waitlist emails. Nothing you type is stored or sent, only your score. Each day's passage is the same one the app's Daily uses, so the web game and the app share their content.

Decisions & iterations

The first plan was sound that reacts to how hard you hit each key. I tested the MacBook's motion sensor for it, and it works, but reading it needs admin access, an extra prompt during setup and an API Apple doesn't document. Haptyk already does it. So I cut it to Dynamic, which changes the sound with the rhythm of your typing instead. It works on every Mac and every keyboard, and when I tried it, it felt good enough.

Volume took longer than I expected. Key sounds were far louder at full Mac volume than at one bar, and fully separate volume isn't possible, because macOS turns every app down after it plays. So Tapit reads the Mac's volume and cancels it out: quieter when the Mac is loud, louder when it's quiet, up to a ceiling. Getting it right meant measuring the real volume curve of the MacBook's speakers, because the one macOS reports is a straight line that isn't true.

I also learned that anything sitting over my work while I type has to be close to invisible. I built a floating speed gauge with comic-book bursts, tried it live and dropped it the same day because it was too distracting. A speed number next to the menu bar icon went the same way. Bigger visuals now live only where you go on purpose to look: Stats and the Playground.

The biggest change came when I started thinking about marketing it. Until it's notarised, nobody can install the app without a warning, so a product page had nothing to offer the people it brought in. The answer was already inside the app. I'd built a typing game into its Playground mode, and I kept playing it myself to push my words per minute up. A daily version of that, on the web, would market Tapit better than a product page. Daily typing tests already exist, but they're ordinary tests that change with the date. None give you one scored shot and then show you where you placed against everyone else that day. So the website became Tapit Daily: five short rounds, the same for everyone, one scored run, then your placement and a Keyprint, your keyboard coloured by how quick each key was. The Mac app became the waitlist at the end of every run.

Real players changed it within days. The first time I shared it in a group chat, a friend got stuck on a capital letter with no idea why, so strict rounds now name a missing Shift on the first miss, and with sound on, a wrong key buzzes, in a sound you can pick. Others said the rounds were just a bunch of text. So two of them became Punctuation and the Ticker, where a line speeds up from 30 to 100 words a minute and you have to stay ahead of it.

Outcome

Tapit Daily has been live at tapitdaily.com since 3 November, and 16 people played the day I first shared it in a group chat. The Mac app works, but it isn't released yet. Before anyone else can install it without a warning it needs Apple's notarisation, which means a paid developer account, and the $4.99 Pro tier needs its store set up. Until then the Daily is how people find Tapit, and the waitlist is how they'll hear when it's out. It's also started to spread: after it went round a group chat, Israeli friends asked for a Hebrew version, so I'm building one for people learning Hebrew, which is in its test week now.

Credits & tools
Solo: design, build and sound packs — Alfie ReesSwift 6 · SwiftUI · AVAudioEngine · JavaScript · VercelLive at tapitdaily.com · building
Case file 03 of 07