Question About In-App Purchases

Ask for Help
1

Hello,

I’m currently developing a mobile application using Glide as the frontend. My goal is to publish the app on both the Apple App Store and Google Play Store with native monthly and yearly subscriptions using RevenueCat.

I initially wrapped the Glide app using another wrapper platform, where I successfully:

  • Built the complete Glide application.
  • Configured RevenueCat.
  • Created monthly and yearly subscription products.
  • Configured RevenueCat offerings and paywalls.
  • Planned to use Make.com to synchronize subscription status back to Glide.

However, I encountered a major limitation.

The wrapper relies on JavaScript methods such as:



const purchases = new NativelyPurchases();

purchases.login(userId, userEmail, callback);

purchases.showPaywall(true, "default", callback);

// or

purchases.purchasePackage("$rc_monthly", callback);

The issue is that Glide buttons cannot execute custom JavaScript, so when a user taps the subscription button, there is no way for Glide to call these native purchase methods. As a result, nothing happens when the subscription button is pressed.

Before I migrate my project to your platform, I’d like to know whether your wrapper supports this workflow.

Specifically:

  1. Can a Glide button trigger a native RevenueCat paywall or purchase?
  2. If yes, how does Glide communicate with the native wrapper?
  3. Do you provide a URL scheme, deep link, JavaScript bridge, or another mechanism that Glide can use?
  4. Can I identify users by passing the Glide RowID and Email to RevenueCat before displaying the paywall?
  5. Is this workflow officially supported for both iOS and Android?

My intended flow is:



Glide App
      ↓
Wrapper
      ↓
RevenueCat Paywall
      ↓
Apple / Google In-App Purchase
      ↓
RevenueCat Webhook
      ↓
Make.com
      ↓
Update Glide subscription status

If this workflow is supported, I’d appreciate any documentation or examples you can share before I migrate my project.

Thank you.