Why I build for iPhone first
12 Nov 2026 · Yash Rawat
By day I build web interfaces. So when I started making my own apps, the obvious move would have been something cross-platform that ships everywhere at once. Instead, every app in the lineup so far starts on iPhone. That wasn't loyalty to a logo. It came down to what each app needed to do, and what one person can realistically build, test and support well.
1The best features live in the system, not the app
Each of my apps leans on something only the operating system can do. The Momentum gym alarm is a real system alarm, so it rings even when your iPhone is on Silent. Your running workout and rest timer sit on the Lock Screen and in the Dynamic Island as a Live Activity, with buttons to log a set without unlocking. Workouts save to Apple Health and close your Activity rings, and widgets put your streak on the Home Screen.
Darkmatter is built directly on Apple's camera system: manual ISO and shutter, RAW and Apple ProRAW. FocusBlock can block apps only because Apple's Screen Time framework lets it. None of these are things a wrapper or a web view can fake. They're the reason the apps are worth keeping, so I build where they're first-class.
2Privacy is part of the platform
My rule for every app is no ads, no tracking, no filler. iOS makes that rule easier to keep, because a lot of the privacy is enforced by the system rather than promised by me.
- Screen Time hands FocusBlock anonymous tokens, so it never learns which apps you chose to block or how you use them.
- Darkmatter asks for add-only Photos access: it can save new shots, but it can't read anything already in your library.
- Every permission is a system prompt you can change later in Settings, not a toggle buried in my app.
Here's what that looks like in FocusBlock. Even the code can't see what you chose, only a Set of tokens to hand back to Screen Time:
import FamilyControls
// Ask once; the person approves in a system sheet, not in my UI.
try await AuthorizationCenter.shared.requestAuthorization(for: .individual)
// What they pick comes back as opaque tokens, never app names.
@State private var selection = FamilyActivitySelection()
let blocked = selection.applicationTokensWhen the platform does the protecting, “we collect nothing” isn't just a line in a privacy policy. It's how the app is physically built.
3One person, one platform, every pixel
I design, build and support everything myself, and a real person answers every support email. That only works if the surface area stays small. Building natively in SwiftUI for a focused set of iPhones means I can get the details right: the haptic tick on every stop of Darkmatter's dials, a one-tap set log in Momentum, a framing grid that matches the photo exactly. Spread across every platform at once, those details would be the first thing I'd cut.
4Clear rules, honestly explained
iOS has firm limits. Apps can't change an iPhone's fixed aperture, can only set ISO and shutter speed manually together, and can only block other apps through Screen Time. Sometimes that's frustrating. But the rules are documented and the same for everyone, so I can design around them and tell you about them up front instead of shipping something that half-works. I wrote more about that in the FocusBlock post on what Screen Time does and doesn't let you do.
5iPhone first, not iPhone only
Choosing iOS first is about where an app works best, not about leaving anyone out. When the idea doesn't depend on iPhone-only features, it can go wider, to the Mac or to Android.
The short version
I pick the platform that lets each app do its one job best, keeps your data yours, and lets one developer polish every pixel. So far, for alarms, cameras and focus, that's been iPhone.