diff --git a/content/docs/expo/guides/using-revenuecat.mdx b/content/docs/expo/guides/using-revenuecat.mdx index 8531c7e6..43bdb96c 100644 --- a/content/docs/expo/guides/using-revenuecat.mdx +++ b/content/docs/expo/guides/using-revenuecat.mdx @@ -7,6 +7,8 @@ description: "If you want to use RevenueCat to handle your subscription-related Not using RevenueCat? No problem! Superwall works out of the box without any additional SDKs. +You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode. + You can integrate RevenueCat with Superwall in one of two ways: - [`CustomPurchaseControllerProvider` component (recommended)](#custompurchasecontrollerprovider-component) diff --git a/content/docs/using-revenuecat.mdx b/content/docs/using-revenuecat.mdx index e30eeed0..b7423aa8 100644 --- a/content/docs/using-revenuecat.mdx +++ b/content/docs/using-revenuecat.mdx @@ -7,6 +7,8 @@ description: "If you want to use RevenueCat to handle your subscription-related Not using RevenueCat? No problem! Superwall works out of the box without any additional SDKs. +You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode. + Integrate RevenueCat with Superwall in one of two ways: 1. **Using a purchase controller:** Use this route if you want to maintain control over purchasing logic and code. diff --git a/content/shared/using-revenuecat.mdx b/content/shared/using-revenuecat.mdx index 6c45f1e7..ce59eab6 100644 --- a/content/shared/using-revenuecat.mdx +++ b/content/shared/using-revenuecat.mdx @@ -7,6 +7,8 @@ description: "If you want to use RevenueCat to handle your subscription-related Not using RevenueCat? No problem! Superwall works out of the box without any additional SDKs. +You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode. + You can integrate RevenueCat with Superwall using several approaches: 1. [**Using a purchase controller:**](#using-a-purchase-controller) Use this route if you want to maintain control over purchasing logic and code. diff --git a/content/shared/web-checkout/using-revenuecat.mdx b/content/shared/web-checkout/using-revenuecat.mdx index 935db7d8..f1651d45 100644 --- a/content/shared/web-checkout/using-revenuecat.mdx +++ b/content/shared/web-checkout/using-revenuecat.mdx @@ -9,6 +9,8 @@ After purchasing from a web paywall, the user will be redirected to your app by If you're using Superwall to handle purchases, then you don't need to do anything here. +You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode. + If you're using your own `PurchaseController`, you should follow our [Redeeming In-App](/web-checkout-linking-membership-to-iOS-app) guide. ### Using a PurchaseController with RevenueCat