watchOS In-App Purchases: A First Look at StoreKit on watchOS 6.2
When Apple shipped the Xcode 11.4 beta builds, the StoreKit changes went beyond price-change consent APIs: watchOS gained in-app purchase support. This guide walks through what the purchase flow looks like on the watch, where it still asks for a password, and what to weigh before adding purchases to a watch app.
What changed for watchOS purchases
The Xcode 11.4 beta release notes introduced support for the next minor releases of iOS, watchOS, and macOS. Alongside a handful of StoreKit APIs around price change consent, the notable addition was in-app purchase support on watchOS. That means a watch app can present a purchase flow on the watch itself. The source does not document whether the transaction avoids the paired iPhone entirely; in the sandbox case, password entry may still happen on the phone.
The practical question for developers is not whether the API exists, but whether the flow feels native enough on a small screen. The behavior observed on watchOS 6.2 is the reference point below.
How the purchase flow behaves on the watch
Two behaviors stood out when testing the flow on watchOS 6.2:
- Password entry in sandbox. In the sandbox environment, a password is required. It can be typed on the watch itself, which is slow and awkward, or entered on the paired phone. The hope is that a watch already on the wrist and authenticated would skip this step, ideally using the same authentication approach Apple Pay on the watch relies on.
- Familiar modal pattern. The modals and messaging closely mirror what users already see on iOS, so the interaction model is not a new one to learn.
A screenshot of the flow as seen from watchOS is included with the original post and shows the purchase modals in context.
A checklist before adding purchases to a watch app
Use these questions to decide whether watch-side purchasing is worth the effort for your app:
- Is the watch a primary surface? If most sessions happen on the wrist, an upgrade path there may reduce friction. If the watch is a companion, the phone flow may be sufficient.
- Does the product fit a tiny screen? Subscriptions with long descriptions or multi-step offers may not translate well.
- Can you tolerate the sandbox password step? Plan for testers to enter credentials, and consider whether production authentication will differ.
- Is the modal pattern consistent with iOS? Reusing familiar messaging reduces confusion.
- Do you need to measure impact? Track whether watch-originated purchases are meaningful before investing further.
Field and control map of the observed flow
The purchase flow on watchOS 6.2 involves a small set of user-facing elements:
- Product selection — the item the user chooses to buy.
- Confirmation modal — mirrors the iOS pattern with price and product details.
- Authentication prompt — requests a password in the sandbox case; may be entered on the watch or the paired phone.
- Completion state — confirms the transaction.
This map is based on the flow as observed in the beta; exact labels and ordering may vary by app and OS version.
Outlook
Whether watchOS purchases become a meaningful revenue channel depends on how apps with heavy watch usage adopt them. For apps where the watch is central, offering an upgrade on the wrist could capture intent that would otherwise be lost. For most apps, the impact is likely modest. At the time of the beta, the plan was to have SDK support available on day one of watchOS 6.2 shipping, so developers could test the flow as soon as it was released.
Frequently asked questions
Why does watchOS ask for a password during in-app purchases?
In the sandbox environment on watchOS 6.2, a password is required to complete a purchase. It can be entered on the watch or on the paired iPhone. The expectation is that production authentication may leverage wrist detection and an Apple Pay-style mechanism, but that behavior was not confirmed in the beta.
Is the watchOS purchase flow different from iOS?
The modals and messaging closely follow the iOS pattern. The main difference observed was the password requirement in sandbox and the small-screen context.
When did SDK support for watchOS purchases arrive?
At the time of the beta, the plan was to add support to the Purchases SDK ahead of watchOS 6.2 shipping, so developers could test the flow during the beta period.