watchOS developer
An Apple Watch app gets a few seconds of someone's attention — often while they're moving. That forces choices: what belongs on the wrist, and what should stay on the phone?
What I do for watchOS
- Native watchOS in Swift & SwiftUI, with complications and widgets that show exactly the right glanceable info.
- Workout and health flows with HealthKit, in the background and energy-efficient.
- The watch app as an extension of the iOS app, not a separate island.
- Energy and performance first. On the wrist, every milliamp and every millisecond counts.
Why me
Ten years of native iOS, and if it runs on an Apple device I build it — watch included. But for sports and health apps I have an edge: I run ultras and do cross triathlons. I know first-hand what you want to see on a sports watch, and especially what you don't.
Honest about scope
Not everything belongs on the wrist. Sometimes the strongest advice I give is "leave this on the iPhone". Pushing back comes with the job: a watch app that tries to do too much is one nobody uses. I help decide which few things actually matter.
Discuss your project