StoreKit 1 deprecation and the other WWDC 2024 changes for subscription apps
Apple's 2024 developer conference brought one clear directive and a cluster of smaller changes that affect how subscription apps sell, retain, and test. The headline is that the original in-app purchase APIs are now formally deprecated. The rest are optional improvements worth evaluating against your roadmap.
StoreKit 1 is deprecated: what changes and what to do
Apple has deprecated the full set of original StoreKit 1 APIs, now labeled the "original API for in-app purchase." This follows the earlier deprecation of the verifyReceipt endpoint. Existing calls continue to function for the time being, but the direction is unambiguous: new work should target StoreKit 2, and existing integrations should be scheduled for migration.
A practical sequence:
- Inventory every place your app still calls StoreKit 1 APIs, including receipt validation paths.
- Identify which flows depend on verifyReceipt and map them to StoreKit 2 transaction and entitlement handling.
- Plan the migration before Apple removes support, not after a breakage appears.
If you use a subscription infrastructure provider, confirm how it handles the transition. Treat any specific vendor commitment as something to verify directly with that vendor.
Win-back offers: re-engaging churned subscribers
Win-back offers give you a way to reach subscribers who have already left, using a discount or a free trial as the incentive. You set them up in App Store Connect following the same general pattern as introductory offers, but the distinguishing feature is a set of eligibility conditions you define.
The conditions can combine:
- How long the user's paid subscription was lapsed
- Time since the user was last subscribed
- Time since the last win-back offer was redeemed
Eligible users can encounter the offer in three places: prominently on App Store product pages, automatically inside the app at launch if you enable that, and through offer links you distribute on your own channels.
Keep two ideas separate when planning messaging. Distribution reach is broad — an offer link can go anywhere. Redemption eligibility is narrow — only users who satisfy your configured conditions can actually complete the offer. Sending links to ineligible users creates a dead end, so segment your outreach against the same conditions you set in App Store Connect.
Streamlined purchasing changes where the transaction finishes. By default, a user can complete a win-back purchase right in the App Store without opening your app. If you opt out, your app receives a PurchaseIntent on launch and you run the purchase flow yourself. Apple also said its editorial team may feature win-back offers across the App Store; the exact form was not yet clear at the time.
StoreKit views: cleaner tier presentation and more control styles
StoreKit views arrived the year before as a lightweight route to a basic paywall. The 2024 update focuses on how tiers are presented and how much visual control you get.
SubscriptionOptionGroup is the new grouping mechanism. It lets you bundle products so each subscription tier reads as a distinct choice, with the paywall showing one group at a time and tabs for switching between tiers.
Three standard control styles join the set:
- Compact Picker
- Paged Picker
- Paged Prominent Picker
If none of those fit, you can assemble a custom control style from the same primitive components the standard styles are built on. That keeps a bespoke paywall consistent with the system-provided look rather than drifting into a separate design language.
App Store quality-of-life updates
Several App Store Connect and App Store changes reduce routine friction:
- Screenshot requirements: apps now need only one screenshot size per platform.
- Featuring nominations: developers can tell App Store editorial about upcoming launch or major-update dates, which may help with featuring around a launch.
- Marketing asset creation: a new App Store Connect tool helps produce promotional images quickly; featured apps also receive a notification with marketing assets for social promotion.
- Custom product page deep links: on first launch, apps with multiple custom product pages receive a deep link identifying which page the user downloaded from, enabling onboarding that matches that page.
- TestFlight: the install page can include screenshots and looks closer to the App Store, making the app's purpose clearer to testers.
- App Store search: personalized suggestions and recent searches appear in a dropdown.
- App Store Analytics API: richer anonymized data is available to third-party tools, and hundreds of new metrics are available to developers as part of Apple's DMA compliance.
In-app purchase testing enhancements
StoreKit configuration files remain the recommended way to test in-app purchases locally, and Apple added several capabilities:
- Privacy policy and license configuration
- Subscription group display name localization
- Win-back offer configuration and eligibility toggling
- In-app purchase images for StoreKit view testing
- Disabling system dialogs to make UI automation testing easier
The transaction manager also gained updates: purchase intents can be sent into apps directly from Xcode, and Billing Issue messages can be tested using the new billing retry option in the StoreKit configuration file.
AdAttributionKit: Apple's new attribution framework
AdAttributionKit is the framework Apple introduced for measuring ad campaigns while keeping user data private. Notably, no SKAdNetwork 5.0 appeared alongside it, which points to AdAttributionKit as the intended path forward rather than an addition to the existing system.
Two capabilities stand out:
- Broader compatibility: it works across the Apple App Store and emerging third-party app stores, giving advertisers more placement flexibility.
- Re-engagement campaigns: advertisers can now measure users who already installed the app and are being targeted again with remarketing ads. A conversion-type field distinguishes download, redownload, and re-engagement, so you can judge which kind of campaign produced the result.
AdAttributionKit carries forward SKAdNetwork's core ideas and looks positioned to succeed it. Treat that succession as the direction Apple signaled, not as a guarantee about SKAdNetwork's retirement timeline.
A decision checklist for your team
Use this to sort the announcements by urgency:
- StoreKit 1 migration — act now. Inventory APIs, map verifyReceipt flows, and schedule the move to StoreKit 2.
- Win-back offers — evaluate. Confirm eligibility rules, decide whether to use streamlined purchasing or opt out, and plan messaging that respects eligibility gating.
- StoreKit views — pilot. Try SubscriptionOptionGroup and the new control styles against your current paywall.
- Testing enhancements — adopt. Add win-back configuration, billing retry, and dialog suppression to your test plans.
- AdAttributionKit — assess. Determine whether re-engagement tracking and third-party store compatibility fit your acquisition strategy.
- App Store quality-of-life updates — apply where relevant, especially screenshot reduction and custom product page deep links.
Frequently asked questions
Do StoreKit 1 APIs still work after deprecation?
Yes, they continue to function for now. Deprecation signals that Apple expects developers to move to StoreKit 2; it does not mean the APIs stop working immediately. Plan the migration before support is removed.
Can anyone who receives a win-back offer link redeem it?
No. Offer links can be distributed through your own channels, but only users who meet the eligibility criteria you configured can redeem the offer.
What happens if an app opts out of streamlined purchasing for win-back offers?
The app receives a PurchaseIntent on launch, which lets it start the purchase flow inside the app instead of completing the purchase in the App Store.
Is AdAttributionKit a replacement for SKAdNetwork?
It builds on SKAdNetwork fundamentals and appears to be its successor. SKAdNetwork 5.0 was not announced alongside it.