WWDC 2023 highlights for subscription apps
WWDC 2023 brought several practical changes for teams building subscriptions and in-app purchases on Apple platforms. The most useful ones for developers are faster paywall building with StoreKit views, stronger StoreKit testing, a few new StoreKit 2 data fields, a quicker route into subscription management, and a clear signal to move away from verifyReceipt.
StoreKit views: a faster first paywall
SwiftUI gained three ready-made views for commerce screens: ProductView, StoreView and SubscriptionStoreView. Each renders your in-app purchase products, so a basic paywall can be assembled without drawing every product row from scratch.
Customisation covers background colour or imagery, links to terms of service and privacy policy, and optional auxiliary buttons such as sign-in. Treat this as the fastest route to a working paywall, then weigh whether its limited styling and layout control fits your brand and conversion testing needs.
StoreKit testing tools: Transaction Manager and simulated failures
Two testing upgrades stand out. First, the Transaction Manager now collects your testing apps for every device and simulator in one place, and you can create a purchase directly from the Mac. That removes the need to start each purchase on a phone or simulator and makes cross-device sync checks much simpler.
Second, Xcode StoreKit configuration files gained a Configuration Settings section at the top. It holds the default storefront and purchase options that previously lived in the Editor menu, plus a new Simulated StoreKit Failures area. There you tick a StoreKit 2 API, pick the error it should throw, and your app receives that configured error when it calls the API during a run. Practise the failure path deliberately: check the box, choose the error, run, and confirm the UI recovers gracefully.
New StoreKit 2 fields worth adopting
StoreKit 2 added a small set of fields that answer questions developers previously had to infer. On the transaction, storefront and storefrontCountryCode identify where the purchase happened. The reason field separates a purchase the customer started themselves from an automatic subscription renewal. In RenewalInfo, under Product.SubscriptionInfo, nextRenewalDate shows when the next renewal is due to be processed.
These fields are available for apps built with Xcode 15, and most work retroactively with earlier iOS versions when using StoreKit 2, so adoption does not require waiting for every user to upgrade the OS.
Quicker subscription management, and verifyReceipt deprecation
Apple's manage subscriptions sheet can now open directly on a specified subscription group instead of landing at the top level and forcing a tap into the right group. For apps with several groups, deep-linking to the relevant group shortens the path to cancelling, switching or reviewing a plan.
Separately, Apple's documentation now marks the verifyReceipt web service endpoint as deprecated. If your validation flow still calls it, put a migration to a newer receipt-validation method on your roadmap rather than building new features on the old endpoint.
Adoption checklist
Use this as a short adoption checklist:
- Prototype a paywall with StoreKit views to compare speed against your custom design.
- Centralise test apps in the Transaction Manager and create test purchases from the Mac.
- Add simulated StoreKit failures for every API your purchase flow depends on.
- Read storefrontCountryCode, reason and nextRenewalDate where they replace inferred logic.
- Deep-link the manage subscriptions sheet to the relevant subscription group.
- Inventory any verifyReceipt calls and schedule their replacement.
| Field | Where it appears | What it tells you |
|---|---|---|
| storefront | Transaction model | The storefront for the transaction |
| storefrontCountryCode | Transaction model | The country the transaction occurred from |
| reason | Transaction model | Whether the customer initiated the purchase or it was an automatic renewal |
| nextRenewalDate | RenewalInfo under Product.SubscriptionInfo | When the subscription renewal is due to be processed |
Fields described as available for apps built with Xcode 15, with most working retroactively on earlier iOS versions when using StoreKit 2.
Frequently asked questions
What are StoreKit views and when do they make sense?
They are SwiftUI views named ProductView, StoreView and SubscriptionStoreView that render in-app purchase products for a paywall. You can adjust background colour or imagery, add terms and privacy links, and optionally include auxiliary buttons such as sign-in. They suit a quick first version, with the trade-off that customisation is more limited than a fully custom paywall.
How does the updated Transaction Manager help multi-device testing?
The Transaction Manager now gathers testing apps across devices and simulators in one place, and lets you create a purchase from the Mac instead of submitting it on a phone or simulator. That makes checking that a purchase syncs across several Apple devices faster.
What can Simulated StoreKit Failures do in Xcode?
In the Xcode StoreKit configuration file, a new Configuration Settings area holds the default storefront and purchase options, while Simulated StoreKit Failures lets you tick an API, choose an error for it to throw, and see your app receive that error at runtime. Use it to prove error handling before release rather than hoping failures happen in production.
Which new StoreKit 2 fields are most useful for subscription logic?
storefront and storefrontCountryCode identify the transaction country, reason distinguishes a customer-initiated purchase from an automatic renewal, and nextRenewalDate in RenewalInfo under Product.SubscriptionInfo shows when renewal is due to be processed. They are available with Xcode 15 builds and most work retroactively with earlier iOS versions when using StoreKit 2.
What changed in the manage subscriptions sheet?
The sheet can now open directly on a specified subscription group, so a customer does not need to tap through groups to find the one they want.
Is verifyReceipt still recommended?
Apple has marked the verifyReceipt web service endpoint as deprecated in its documentation. Teams still using it should plan a migration to a newer receipt-validation method.