Rob Mulder, Senior Native Mobile Developer. Apple Watch, native in Swift and SwiftUI.

Specification

STACK

Swift, SwiftUI and Swift 6 strict concurrency. HealthKit and background tasks where the app needs them.

PLATFORMS

watchOS next to iOS, iPadOS, tvOS, CarPlay, macOS and Android. From one pair of hands, no handover.

BACKGROUND

CoronaMelder: wrote the background task that woke millions of phones silently. 557 commits, second largest contributor.

TESTED

Unit, snapshot and UI tests plus CI/CD are part of the job. Dumpert for Apple TV has 41 unit tests, open source.

Does this belong on the wrist or on the phone?

Users are training and want their numbers while they move

PickA native watch app with a HealthKit workout session

WhyA running workout session keeps the app working with the screen off and the phone in a bag.

One number or status has to be visible at a glance

PickA complication plus a widget, not a full app UsuallyThis is the usual answer.

WhyA complication already sits on the watch face, costs little battery and does not load first.

The flow needs text input, filters or a long form

PickLeave this on the iPhone

WhyTyping and scrolling on a wrist screen costs more time than reaching for the phone. On the wrist, only confirm.

Notifications are the only goal

PickNo watch app, rich notifications are enough

WhywatchOS already shows iOS notifications on the wrist, so adding an app buys you nothing.

There is no iOS app yet, only a watch idea

PickThe iOS app first, the wrist after that

WhyThe model, the account and the tests come from the iOS app. Without that base you build it twice.

Read on