RefactorUI: Clean API Architecture

[facumenzella]

Summary

🎯 New API Structure

The refactored API provides a clean, consistent interface that's easy to discover and use:

Static Presentation API

// Present a paywall
await RevenueCatUI.PaywallsPresenter.Present(options);

// Present paywall only if needed (user lacks entitlement)
await RevenueCatUI.PaywallsPresenter.PresentIfNeeded("premium", options);

// Check platform support
bool supported = RevenueCatUI.PaywallsPresenter.IsSupported();

Configuration & Results

// Configure paywall presentation
var options = new RevenueCatUI.PaywallOptions
{
    OfferingIdentifier = "premium",
    DisplayCloseButton = true
};

// Handle results
RevenueCatUI.PaywallResult result = await RevenueCatUI.PaywallsPresenter.Present(options);

switch (result.Result) 
{
    case RevenueCatUI.PaywallResultType.Purchased:
        // User completed a purchase! 🎉
        break;
    case RevenueCatUI.PaywallResultType.Cancelled:
        // User dismissed the paywall
        break;
    case RevenueCatUI.PaywallResultType.Error:
        // Something went wrong
        break;
    case RevenueCatUI.PaywallResultType.NotPresented:
        // Paywall wasn't shown (user already has entitlement)
        break;
}

MonoBehaviour API

// For scene-based usage
var behaviour = GetComponent<RevenueCatUI.PaywallsBehaviour>();
await behaviour.PresentPaywall(options);
await behaviour.PresentPaywallIfNeeded("premium", options);

🔧 What Changed

✅ Added

• RevenueCatUI.PaywallsPresenter - Main static API class with clean method names
• RevenueCatUI.PaywallsBehaviour - MonoBehaviour component for scene integration
• Consistent naming - All classes follow Paywalls* convention

The new API delivers exactly what developers expect: clean, discoverable methods that do exactly what their names suggest, with no confusion about namespaces or redundant parameters. 🚀

[facumenzella]

I'l remove Internal

[vegaro]

Should this be RevenueCatUI

[vegaro]

is this needed?

[vegaro]

oh yes for PaywallsPresenter