subscription-manager

You can manage in-app subscription states and credit balances by using an @Observable SubscriptionManager class that wraps Purchases.shared to track premium status and handle feature gating.

Feature gating with RevenueCat works by checking user subscription status or available credits, enabling or disabling specific app features based on the active entitlement ID fetched dynamically from StoreKit.

To prevent hardcoded pricing, you fetch prices dynamically from StoreKit through the RevenueCat integration, avoiding custom plan models and ensuring package prices load directly from the store configuration.

Yes, you need a RevenueCat API key and an entitlement ID to configure the SubscriptionManager, which is required to load packages, process purchases, and track premium or free subscription states.

The best way to architecture subscriptions and credits is using a singleton @Observable class to consistently manage package loading, purchasing, and status updates across your entire application.

You should not use custom plan models because they bypass dynamic price fetching from StoreKit, which breaks consistency and risks displaying incorrect pricing across your subscription management implementation.