Questions

Hi Median team,

I'm building an app on Base44 (a no-code web app builder) and want to wrap it with Median to add native RevenueCat-powered in-app purchases/subscriptions. Base44 doesn't support native StoreKit/Play Billing directly, so I'm evaluating Median as the wrapper layer instead.

A few questions before I commit:

RevenueCat plugin coverage

Does your RevenueCat plugin expose bridge methods for all of: purchase, restorePurchases, getCustomerInfo, getProductInfo, and manageSubscription? If manageSubscription isn't directly supported, how do users manage/cancel from within the app?

Base44 compatibility
2. Is there anything about Base44-hosted apps specifically (WebView output, CSP, domain/cookie handling) that could limit the RevenueCat plugin's JS bridge from working correctly?
3. My subscription product (herhealth_pro_monthly) has a 14-day free trial configured in App Store Connect — does that flow through automatically via the plugin, or does it need separate handling?

Build & submission
4. Once the plugin is enabled and configured, does Median handle the full build, signing, and App Store Connect upload, or do I still need manual steps?
5. What exactly do I need to provide upfront (Apple Issuer ID, Key ID, .p8 key, Team ID), and what do you generate for me?
6. What's the realistic turnaround time from enabling the plugin to having a TestFlight build ready?

Testing
7. Can I run Sandbox purchase and restore testing on a Median TestFlight build using a standard Sandbox tester account?
8. Do I need to change my app's existing IAP-detection logic (currently checking for window.RevenueCat) to instead check for Median's JS bridge, or can I bridge the two?

Pricing
9. What plan/tier is required for the RevenueCat native plugin specifically?

I'm on a tight timeline for App Store review, so any guidance on the fastest realistic path would help a lot. Thanks!