Flutter SDK
Install once, then show any paywall with a trigger key.
BUILD IT. PUSH IT. MAKE IT YOURS.
Design, target and A/B test mobile paywalls from one dashboard, or let your AI agent build them for you. Push every change to your app without waiting for a release.
A product by Apphara
Personal plans. Unlimited workouts.
Every reason to keep going.
More ideas. More possibilities.
Your creativity, without limits.
Guided sessions. Better sleep.
A little space to breathe.
Sample app paywalls · Illustrative designs & pricing
EVERYTHING IN ONE PLACE
Watch how MySuperWall works. Manage all of it from one dashboard, without waiting for an app update.
Screens shown are animated recreations of the live interface with sample data.
NEW · CHAT WITH YOUR DATA
Connect Claude Code, Codex or Cursor to your app and chat with everything it knows: paywalls, triggers, users, events and experiments. Plain language in, real numbers out.
Everything you need to build, ship and improve your paywall.
Install once, then show any paywall with a trigger key.
Show a follow-up paywall when someone dismisses the first.
Load paywalls before they are needed so they open without waiting.
Connect RevenueCat to see revenue from real, verified purchases.
Check App Store and Google Play receipts on the server.
Let your AI agent design paywall drafts from a prompt. You review and publish.
Ask Claude Code, Codex or Cursor about your triggers, users and conversion. Read-only.
Invite teammates and give each person only the apps they need.
See who changed what, with entries you cannot edit.
Store keys are encrypted at rest and never shown again.
Every published version is kept. Restore an earlier one and it goes live as a new version.
Hold back a share of users to see what a paywall really adds.
Not limited to templates. Build any layout that runs in a WebView.
FROM IDEA TO EXPERIENCE
Design in your dashboard. Deliver in your app.
Start with a template or use HTML and CSS to make the experience your own.
Define the trigger key for the screen or action where your paywall belongs.
Use the Flutter SDK to retrieve and display the configured paywall.
// Fetch the experience for this moment.
final paywall = await MySuperWall.getPaywall(
triggerKey: 'onboarding_finish'
);
// Display your configured paywall.
if (paywall != null) {
showPaywall(context, paywall.html);
}WebView-based rendering gives you room to build beyond a fixed layout.
PRICING
Publishing paywalls is free, with no card needed. Premium adds testing and targeting tools when you are ready, and your first month is on us.
$0forever
Start right now. No card, no time limit.
$9.99/ month after your free month
Optional. Add experiments, targeting and more whenever you are ready. Try it free for a month.
Prefer yearly? $99.99 a year (about $8.33 a month). First month free too.
Try Premium free for a monthYour first month is free. Cancel any time and you keep Premium until the end of the period you paid for.
We do not take a cut of what your app earns, so your growth stays yours.
$9.99 a month, whether your app has ten users or ten million. No credits, quotas or surprise overages.
No. MySuperWall never touches payments. The paywall tells your app which product the user chose, and your own in-app purchase code (RevenueCat, in_app_purchase or anything else) completes the purchase.
No. Paywall design, texts, products and triggers are fetched when your app runs, so edits reach users without a new build. The SDK itself must be in your app once, and store review rules for your app still apply.
Flutter, native iOS (Swift), native Android (Kotlin) and React Native, all with the same trigger-based workflow.
Yes. Connect Claude Code, Codex or Cursor with an access key and it can design paywall drafts for you, including templates from scratch. It can never publish: you review every draft and decide what goes live.
No. RevenueCat is an optional integration that adds verified revenue to your dashboard. Paywalls, triggers and A/B tests work with whatever billing code you already have.
Yes. Split a trigger between two paywalls; each user always sees the same variant. You can also hold back a share of users as a control group and show a recovery paywall when one is dismissed.
Paywalls are cached on the device, so a paywall that was loaded before still opens offline. If nothing is cached and the network fails, the SDK returns "no paywall" instead of blocking your app.
Yes. Each paywall can have several languages, with machine translation to get you started. The SDK picks the language you set.
Store credentials are encrypted at rest and never shown again. Each account only sees its own apps, access keys can be revoked at any time, and every change is logged. You can delete your account and all of its data yourself.
Your app key, your bundle ID or package name, the platform and app version, a user ID (an anonymous one is generated if you do not set your own), and paywall events such as views, purchase taps and dismissals.
MySuperWall is free during early access. Paid plans are being prepared as a fixed subscription with no share of your revenue. Prices have not been announced yet.
SEE IT IN ACTION
Pick a template, make it yours, publish it and A/B test it. No app update, no waiting for review.
MAKE YOUR NEXT ITERATION COUNT
Bring your paywall workflow together with MySuperWall.