Project 02 / Case study

WakaTime

An alarm that asks you to get up and tap a physical NFC tag to turn it off.

A mobile alarm experience built around a simple promise: the alarm is complete only when you get up and tap your WakaTag Capsule. One account, one phone, one Capsule.

WakaTime architecture and flow diagram
3D HARDWARE MODEL · WAKATAG CAPSULE (.GLB)
FOUNDATION

Alarms learned to travel with you

Cloud save and full alarm restore laid the groundwork for a dependable setup across sessions, with Capsule claims tied to the account.

SECURITY

Capsule claims moved server-side

A server-owned tag registry and callable-only claim and release flows replaced the mobile Firestore fallback. Bindings became append-only history.

RELIABILITY

The wake-up sound became WakaTime's

On iOS, AlarmKit began playing the branded alarm sound, while the handoff into the app was tightened to avoid a silent gap.

PRODUCT

One Capsule, one clear rule

The shipped ownership model settled on one account, one phone, and one Capsule. The Capsule tap remains the only way to confirm a wake-up.

PLATFORM

Sign-in and alarm state got stronger

Email verification codes joined Apple and Google sign-in; alarms gained a local-first mirror and tag pairing moved to regional HTTPS callables.

EXPERIENCE

The details started to feel finished

Branded onboarding, clearer NFC guidance, loop-safe alarm audio, and a more reliable emergency bypass brought more care to the wake-up flow.

POLISH

Morning setup became a little calmer

Alarm labels aligned with the home clock, sound and notification settings were simplified, and sheets adjusted around the keyboard.

← All projects