Apple Watch has a meaningful installed base — on the order of 100+ million active devices — but watchOS apps as a monetization category are nichy. The watch is mostly a notifications/glanceable surface, with some heavy use in fitness. This post is the honest economics.
Market reality
- Apple Watch has surpassed all Swiss watch brands combined in unit sales.
- Watch app usage is dominated by Apple's own apps (Workout, Heart Rate, Activity) and a handful of third parties (Strava, AutoSleep, Carrot Weather).
- Most third-party watch apps are companions to iOS apps, not standalone purchases.
- App Store cut is the same as iOS: 15% Small Business / 30% standard.
Companion vs independent watch apps
- Companion apps — require the iOS app to be installed. Most watch apps are this. Free with the iOS purchase under Universal Purchase.
- Independent watch apps — install directly to the watch from a separate App Store on watchOS. Possible since watchOS 6+. Cellular-equipped watches can run independent apps without an iPhone.
Independent watch apps are a small but real category: meditation, simple games, fitness trackers for users who want to leave the phone behind on runs.
Categories that work on Apple Watch
- Fitness tracking — the dominant category. Running, cycling, swimming, strength training.
- Sleep tracking — high willingness to pay for quality sleep insights.
- Meditation / breathing.
- Notifications and quick actions — e.g., quick reply, smart-home control.
- Complications — the small info widgets on watch faces. High visibility per user.
- Health monitoring — heart rate, ECG, blood oxygen, fall detection apps that complement Apple's health features.
Monetization
Watch apps are almost never sold as standalone products. The economics:
- Free companion bundled with the iOS app's purchase. Most common.
- Subscription for the iOS+Watch combined experience — e.g., $4.99/mo fitness subscription that includes both. Justifies premium pricing.
- One-time purchase for niche utilities — rare but possible.
Technical particulars
- watchOS apps are now native SwiftUI — you reuse most knowledge from iOS development.
- Constraints: tiny screen, small battery, limited CPU. Don't try to ship complex UI.
- Complications appear on watch faces; high visibility for daily glanceable content.
- Health framework access is privileged; HealthKit data is the highest-value integration.
- Limited or no AI use cases — the watch isn't a good surface for conversational AI. AI features should live on the iPhone or backend.
Strategy for iOS developers adding watch
- Don't build a watch app unless your iOS app has natural glanceable value. "Watch version of everything" rarely justifies the effort.
- Lead with complications. Daily-glance content on the watch face is the highest-value Watch surface.
- Universal Purchase — users get the watch app free with the iOS purchase.
- Sync via HealthKit / iCloud when state needs to flow between phone and watch.
- Budget realistically — a polished companion watch app is 2-6 weeks of focused work even with Claude Code helping.
For RDR2 / GTA V Companion: a watch app doesn't fit naturally. Game companions are deeply screen-based and the watch screen is too small for the use case. Skip.