Boop

I founded Boop as a local-first iPhone utility for people who want their compatible WHOOP data in Apple Health without adding another account, subscription, or health-data cloud. Boop communicates directly with WHOOP 5.0 and MG hardware over Bluetooth, processes the supported data on the iPhone, and writes it to HealthKit.

Product Shape

The product is a native SwiftUI app with a direct hardware-to-HealthKit path. The important boundary is deliberate: strap data is collected, persisted, and derived on-device, while the support site documents compatibility, privacy, and methodology without operating a Boop health-data backend.

Explore Boop

The product, the build story, and its support surface live across the Boop site and this portfolio:

What I Built

• BLE Protocol Engineering — Implemented native CoreBluetooth stream decoders and packet parsers for WHOOP 5.0 and MG hardware.
• Local-First & HealthKit — Built the SwiftUI/HealthKit pipeline for offline sync of continuous heart rate, sleep staging, HRV, resting heart rate, and workouts.
• Dual Sync Modes — Architected Preserve Mode as a read-only path that does not alter strap memory, alongside Trim Mode for durable chunk clearing after a successful local save.
• On-Device Processing — Deployed local AI models for physiological insights without sending sensitive health data off-device.
• Release & Support Surface — Shipped the product site with compatibility, privacy, methodology, and external TestFlight guidance for an independent app with no Boop account or subscription.

What I Learned

Boop sits at the seam between reverse-engineered hardware behavior, durable local storage, HealthKit semantics, and a user-facing product. The work taught me to make every handoff observable and recoverable: preserve the strap when a user chooses read-only sync, keep exports idempotent, and make privacy a property of the architecture rather than a promise added after the fact.

Product Gallery