Apple Watch In-App Purchases
A first look at Apple's StoreKit support on watchOS 6.2
Last week, Apple pushed out beta builds for Xcode 11.4, which included support for the next minor release of iOS, watchOS, and macOS. Like any sane person would do, we rushed to see what changes there were for StoreKit. Besides the addition of a few APIs around price change consent, the biggest addition was support for watchOS.
Curious how Apple implemented the flow, we quickly added support to the RevenueCat Purchases SDK, and tried out the purchasing flow on watchOS 6.2.
Some observations:
- At least for the sandbox case, you are required to enter a password. This can be done on the watch (excruciating) or you can grab your phone to enter the password. Hopefully, if the watch is on your wrist and authenticated, you won’t need to do this. Ideally it works with the similar authentication mechanism that Apple Pay on the watch uses.
- The flow pretty much mimics what we’re used to on iOS as far as modals and messaging.
It will be interesting to see how IAP support on watchOS gets used. I’m guessing that some apps with heavy watch usage could try and nab some upgrades on the watch, but my intuition tells me it won’t be a game changer for most apps. Regardless, we’ll have support for IAPs on day one of 6.2 shipping so star our repo to get updates when support is available.
You might also like
- Blog post
“Focus on the problem that you are really passionate to solve” — Francescu Santoni, Mojo
How Mojo grew to over $1M in MRR, the most impactful pricing and paywall experiments, and why it’s important to choose complexity instead of just letting it happen.
- Blog post
RevenueCat SDK 5.0 – The StoreKit 2 Update
The new major version of the RevenueCat iOS SDK makes StoreKit 2 the default
- Blog post
WWDC ’24 recap on the Sub Club podcast — David Barnard, Jacob Eiting, Charlie Chapman
On the podcast: Highlights from WWDC 2024 and what they mean for subscription apps and RevenueCat users.