Developing a Mobile App for Content Subscription (Patreon Model)
Patreon model on mobile hits one key conflict: App Store and Google Play require digital content sold through their IAP (In-App Purchase) with 15–30% commission. But content creator already sells the same content via website cheaper. User sees this, asks uncomfortable questions, and app risks rejection for 3.1.1 violation. Correct architecture starts with legal and technical answer.
IAP vs External Payments: Where's the Line
App Store rules allow "reader apps" (open content bought elsewhere) to link to external site for purchase—with External Link Account entitlement (available in US, EU under DMA, South Korea). Practice:
- Subscription via web—app only opens content, doesn't sell. Review passes if no "Subscribe" CTA inside app leading to IAP, and External Link entitlement where allowed.
- IAP subscription inside app—Apple/Google take 15–30%. But seamless UX, app can offer subscription directly in-app.
- Hybrid—web purchase for new subscribers (external link), IAP for in-app buyers. Legal but complex to maintain two flows.
Content Access Architecture
EntitlementManager—central component. Truth sources about access:
- StoreKit 2 Transaction.currentEntitlements (if IAP).
- Backend subscription status (if web-billing or RevenueCat as aggregator).
On app start: check both sources in parallel, take max access. Server sends JWT with tier, expires_at—client validates signature, caches. Update every 24 hours or on subscription_updated push.
Tier-based access: EntitlementManager.hasAccess(tier: .premium, feature: .exclusivePosts)—single check point. ContentRepository filters feed: locked posts show preview + paywall blur overlay, unlocked—full.
Media Content and DRM
Videos for paying subscribers shouldn't be accessible by direct URL without auth. Scheme: app requests signed_url with 15-minute TTL (/content/{id}/stream?token=...). URL signed on server (CloudFront Signed URL / Google Cloud CDN Signed URLs). AVPlayer (iOS) / ExoPlayer (Android) plays HLS—segment caching automatic via AVAssetDownloadTask (iOS) for offline viewing.
Stricter protection—FairPlay Streaming (iOS) / Widevine (Android). Netflix/Spotify DRM level. Requires license server (integrate via Axinom DRM, EZDRM, BuyDRM). For most creator platforms—overkill, but high-value content justifies.
Audio podcasts usually sufficient without DRM via signed URLs. AVAudioPlayer / MediaPlayer / ExoPlayer for playback, background via AVAudioSession (.playback category) + CommandCenter (iOS) / MediaSession API (Android)—lock screen control.
Post Feed and Creator Interaction
Chronological + algorithmic feed via UICollectionView DiffableDataSource / Jetpack LazyColumn. Pagination—cursor-based (not offset—new posts shift offset). FeedRepository with Paging 3 (Android) or custom PaginatedFeedLoader (iOS).
Comments with real-time update via WebSocket or long polling. Reactions—optimistic update: UI updates immediately, API in background, error rolls back. Standard pattern for low perceived latency.
Live streams (live)—LL-HLS / DASH with AVPlayer / ExoPlayer. Live chat—WebSocket.
Notifications and Engagement
Push on new post from followed creator. On client—per-creator notification settings: user chooses who sends push. Device token stored on server tied to creator_subscription_ids—server sends push only to relevant audience, not broadcast.
Process
App Store / Play Store policy analysis for monetization model → EntitlementManager and billing flow design → feed + media player + paywall → push notifications → QA (subscription edge cases: grace period, refund, restore purchases) → publication.
Timeline Estimates
MVP (post feed, video/audio player, IAP subscription, basic comments): 5–8 weeks. Full creator platform with live streaming, DRM, creator analytics, multiple tier support: 3–4 months.