Feature request
Add support for automatic Exit Offer paywalls to the KMP presentation layer, matching the behavior available in the native RevenueCat Paywall SDKs.
Motivation
We’re using RevenueCat Paywalls in a Kotlin Multiplatform app, but automatic Exit Offers are currently not supported through the KMP presentation API.
Replacing the shared integration with separate native implementations would add significant complexity, especially on iOS, just to access this functionality.
Current workarounds
We’re currently considering:
- Intercepting the initial paywall dismissal and displaying a separate RevenueCat Offering as a custom exit-offer flow.
- Accessing the native RevenueCat Paywall presentation APIs from platform-specific KMP source sets while keeping the existing shared purchase configuration.
Neither option provides straightforward, officially supported feature parity with the native SDKs.
Expected behavior
When an Exit Offer is configured in RevenueCat, the KMP Paywall presentation API should be able to display it automatically on eligible dismissals, with the same purchase handling, analytics, and lifecycle behavior as the native SDKs.
It would also be helpful to know whether this is already planned and whether there is an estimated timeline.
Feature request
Add support for automatic Exit Offer paywalls to the KMP presentation layer, matching the behavior available in the native RevenueCat Paywall SDKs.
Motivation
We’re using RevenueCat Paywalls in a Kotlin Multiplatform app, but automatic Exit Offers are currently not supported through the KMP presentation API.
Replacing the shared integration with separate native implementations would add significant complexity, especially on iOS, just to access this functionality.
Current workarounds
We’re currently considering:
Neither option provides straightforward, officially supported feature parity with the native SDKs.
Expected behavior
When an Exit Offer is configured in RevenueCat, the KMP Paywall presentation API should be able to display it automatically on eligible dismissals, with the same purchase handling, analytics, and lifecycle behavior as the native SDKs.
It would also be helpful to know whether this is already planned and whether there is an estimated timeline.