News · June 9, 2023
WWDC23 gives subscription apps ready-made StoreKit paywall views
Apple used WWDC23 to introduce SwiftUI views that render in-app purchases and subscription offers with very little code, along with new StoreKit testing tools. For small teams this lowers the cost of shipping and iterating on a native paywall.
What happened
- Apple listed Meet StoreKit for SwiftUI among its WWDC23 session highlights on June 9, 2023, according to its developer news page.
- In that session, Apple explains that Xcode 15 brings SwiftUI views for in-app purchases, namely StoreView, ProductView and SubscriptionStoreView, which load product data from the App Store and, for subscriptions, check subscriber status and introductory offer eligibility.
- RevenueCat's WWDC23 summary reported new StoreKit 2 transaction fields for storefront and purchase reason, a next renewal date in renewal info, simulated StoreKit failures in Xcode, and that Apple has deprecated the verifyReceipt endpoint.
Why it matters
SubscriptionStoreView will not replace a carefully designed custom paywall, but it is a solid baseline. It handles localisation, offer eligibility and platform differences that teams often get wrong, and it is a fast way to add purchase screens to secondary surfaces such as settings or an iPad or Mac version.
The verifyReceipt deprecation is the item to put on the roadmap. If your backend still validates receipts that way, plan a move to StoreKit 2 transactions and the App Store Server API, and use the new storefront and purchase reason fields to separate first purchases from renewals in your revenue reporting and in the events you send to ad platforms.
Sources
- Apple Developer News: WWDC23 highlights
- Apple Developer: Meet StoreKit for SwiftUI
- RevenueCat Blog: WWDC 2023 highlights: What's in store for subscription apps
This post is CMM’s own summary and commentary on publicly reported news. Facts are attributed to the sources linked above; please read them for full details. CMM is not affiliated with these publishers or with the companies mentioned, and trademarks belong to their owners. Prepared with AI assistance. Corrections or requests: [email protected]. See our editorial policy.
Want help with this?
Tell us what you need, and we will suggest the right team model on a short call.
Talk to us