In-App Purchases & subscriptions with StoreKit 2 by Yevhenii PetrenkoIn-App Purchases & subscriptions with StoreKit 2 by Yevhenii Petrenko
In-App Purchases & subscriptions with StoreKit 2Yevhenii Petrenko
Cover image for In-App Purchases & subscriptions with StoreKit 2
Monetization is where most iOS apps quietly lose money — a paywall nobody converts on, receipts that don't validate, restores that fail, subscriptions that stay active after a refund.
I build subscription infrastructure that actually holds up in production. All 4 of my App Store apps run on it.
WHAT I BUILD
StoreKit 2 from scratch: products, purchase flow, restore, transaction listener
Server-side receipt validation and App Store Server Notifications v2
Adapty or RevenueCat integration when you want analytics and A/B testing without shipping a new build for every paywall change
Free trials, intro offers, promotional offers, win-back campaigns
Paywall UI in SwiftUI or UIKit — built to be swapped and tested, not hardcoded
Migration from legacy StoreKit 1 to StoreKit 2
WHAT YOU AVOID
Guideline 3.1.1 rejection for a paywall Apple doesn't like
Users who paid and lost access after reinstalling
Revenue you can't explain because nothing is tracked
I test every flow in sandbox before handoff: purchase, cancel, refund, expiry, family sharing, upgrade, downgrade. You get a document listing what was verified.
Tell me what you're selling and I'll tell you the right pricing model for it.
FAQs

Starting at$1,400
Duration2 weeks
Tags
StoreKit
Swift
SwiftUI
iOS Developer
Mobile App Development
Revenue Optimization
In-App Purchases
Subscription Management
Service provided by
In-App Purchases & subscriptions with StoreKit 2Yevhenii Petrenko
Starting at$1,400
Duration2 weeks
Tags
StoreKit
Swift
SwiftUI
iOS Developer
Mobile App Development
Revenue Optimization
In-App Purchases
Subscription Management
Cover image for In-App Purchases & subscriptions with StoreKit 2
Monetization is where most iOS apps quietly lose money — a paywall nobody converts on, receipts that don't validate, restores that fail, subscriptions that stay active after a refund.
I build subscription infrastructure that actually holds up in production. All 4 of my App Store apps run on it.
WHAT I BUILD
StoreKit 2 from scratch: products, purchase flow, restore, transaction listener
Server-side receipt validation and App Store Server Notifications v2
Adapty or RevenueCat integration when you want analytics and A/B testing without shipping a new build for every paywall change
Free trials, intro offers, promotional offers, win-back campaigns
Paywall UI in SwiftUI or UIKit — built to be swapped and tested, not hardcoded
Migration from legacy StoreKit 1 to StoreKit 2
WHAT YOU AVOID
Guideline 3.1.1 rejection for a paywall Apple doesn't like
Users who paid and lost access after reinstalling
Revenue you can't explain because nothing is tracked
I test every flow in sandbox before handoff: purchase, cancel, refund, expiry, family sharing, upgrade, downgrade. You get a document listing what was verified.
Tell me what you're selling and I'll tell you the right pricing model for it.
FAQs

$1,400