Turn your website into the next DDuoTalk

Paste a URL, say an idea or type it. Muaz researches your competitors, designs an original iOS app and ships it to the App Store.

Try
10 competitors foundHushed, TextNow, 2ndLine…
“Add Face ID”Applied in 4s
Build 1.0 (3) passed QAReady for TestFlight
Pull down from the topSwipe up the barTap a notification
The platform

Five product engines. One launch team.

Each engine is a set of specialist AI agents with its own workspace in the dashboard. Together they replace the researcher, designer, developer, release manager and growth marketer.

Built for non-technical founders

Talk to your app like you'd talk to your designer.

No code, no tickets, no waiting. Say what you want changed. Muaz rebuilds only what changed and shows it on a real iPhone in seconds.

Voice edit

“Make the dashboard cleaner.”

The secondary card goes, spacing tightens to a calm 16 pt grid and the layout switches to Minimal Apple.

✓Rebuilt in 3.8 s · version 1.0 (4)
Voice edit

“Change the primary color to blue.”

Every button, tab and highlight picks up the new color from one design token. Nothing to hunt down screen by screen.

✓1 token · 23 components updated
Native feature

“Add Face ID to unlock.”

Muaz adds LocalAuthentication, the permission string Apple requires, and a lock screen that matches your brand.

✓expo-local-authentication added
Design direction

“Make it premium and dark.”

Glass surfaces, a neon glow and bolder numbers. The Premium Futuristic concept, applied to every screen at once.

✓Concept switched · version 1.0 (6)
Growth

“Tell my users we just launched.”

A push notification is drafted, previewed on the lock screen and scheduled. It only sends after you approve it.

✓Push drafted · waiting for your approval
“Make the dashboard cleaner.”
Website Intelligence

Your website becomes the spec.

Muaz reads your public pages, brand and flows, then flags the private APIs it still needs from you.

Native features

Feels native, because it is.

Quality Assurance Agent

38 tests before you ever see it.

App Store top charts

Learn from apps earning millions a month.

Before Muaz designs yours, it studies the patterns behind the App Store's highest-earning and fastest-growing apps across every category. Tap any app to see what it does well.

Templates

Start from a category that already works.

Each template comes pre-researched against the top apps in its category. Tap any phone to explore the screens.

Where we fit

Website-first. Voice-driven. Growth-aware.

Prompt-based builders start from a blank chat. Website-to-app services wrap your site in a WebView. Muaz.io rebuilds your business as a native app and tells you how to grow it.

CapabilityMuaz.ioRorkMedianMobiLoudFlutterFlow
Start from a website URLFull redesign, native UIPrompt firstWebView wrapperDone-for-you wrapperManual
Edit by voiceEvery screen, with historyText chat———
Competitor and revenue research5 / 10 / 20 apps————
Native app outputReact Native + Expo, SwiftUI mode nextSwiftUIHybridHybridFlutter
App Store submissionAgent-prepared, one clickBuilt inAssistedDone for youExport
Growth strategy after launchASO, paywall, 30/60/90 plan——Agency add-on—

Positioning summary from public product pages, November 2026. Competitor plans change often; check their sites before quoting.

Pricing

Start with a prototype. Scale to an agency.

Every plan includes AI credits and build quotas with usage-based top-ups. Apple Developer Program membership is billed by Apple separately.

FAQ

Questions founders ask first

Can a URL alone make my app fully work?

A URL gives Muaz.io your brand, pages, content and flows, so you get a complete designed app. Live data such as accounts, payments or SMS needs your approved API and authentication. The Backend Connector asks for those and maps them to screens. Private backend access is never possible from a URL alone.

Is it a WebView wrapper?

No. The Development engine generates native React Native + Expo screens with real navigation, state and native APIs. A premium SwiftUI generation mode is on the roadmap.

Will it copy my competitors' designs?

No. Competitor screens are inspiration. The Design engine extracts patterns (onboarding length, navigation, paywall layout) and generates original interfaces in your brand.

Who publishes to the App Store?

You do, from your own Apple Developer account. Muaz.io prepares the build, signing, icons, screenshots and metadata and uploads to TestFlight. Final approval always rests with Apple's review team.

Where do competitor revenue numbers come from?

From licensed providers such as Appfigures and AppTweak, plus Apple's public search data. They are estimates, labelled as estimates. Competitors' real profit, CAC, retention or ad spend are not public and are never shown as fact.

Free tool · Paywall teardown

Find out why your paywall is not converting

Answer 15 yes-or-no questions about your paywall. Get a score, the fixes that matter most and a check against the subscription rules in Apple's App Review Guidelines.

Updated Nov 6, 202613 min read · 3,030 words5 cited sources

How to use the paywall teardown

Open your app's paywall next to this page and answer each question honestly. The checks are grouped into four areas: clarity, offer, trust and Apple rules. Your score updates as you answer, and the priority list shows what to fix first. Apple rule items are always listed first, because they can block your app from approval.

The tool runs entirely in your browser. Nothing you select is sent anywhere.

Turn this into a real app

Your tool results are a great start. Paste your website and Muaz.io builds the app around them.

Why the paywall is your most important screen

For a subscription app, the paywall is where revenue is made or lost. A small improvement in conversion compounds across every user who sees it, every month. RevenueCat's 2026 research shows how big the differences can be: hard paywalls reached a median day-35 trial-to-paid conversion of about 10.7%, against about 2.1% for freemium, and generated about $3.09 of revenue per install by day 60, against $0.38.

That does not mean every app should use a hard paywall. It means the design of your paywall, its placement and your offer deserve as much care as any feature.

The four areas the teardown checks

Clarity. Can someone understand the offer in three seconds? The headline should state the outcome, the price per period should be visible without scrolling, the trial terms should be explicit and there should be no more than three plans.

Offer. Is the offer compelling? The best-value plan should be preselected and labelled, annual savings shown, the trial long enough for users to feel value and the paywall placed after a moment of value.

Trust. Does the paywall reassure? Real social proof, a visible "cancel anytime" message and a clear way to close or continue free all reduce anxiety.

Apple rules. Is the paywall compliant? Restore purchases, links to terms and privacy, the billed amount as the most prominent price and auto-renewal disclosure are required under Apple's subscription guidelines.

~5×trial-to-paid, hard paywall vs freemium
+70%conversion for 17–32 day trials vs ≤4 days
35%of annual cancellations in month one

Apple's subscription rules, in plain language

Apple's App Review Guidelines section 3.1.2 sets out what auto-renewable subscriptions must do. In practice, your paywall should:

  • Explain what the user gets with the subscription.
  • Show the price and the billing period for each plan.
  • Make the amount that will be billed the most prominent pricing information. If you show a monthly equivalent for an annual plan, the annual price must be clearer.
  • Disclose that the subscription renews automatically unless cancelled, and how to cancel.
  • Include a way to restore previous purchases.
  • Link to your terms of use and privacy policy.
  • Avoid misleading claims, hidden costs or manipulative tactics, such as making the close button hard to find.

Apple's Human Interface Guidelines for in-app purchase add design advice, such as letting people use the app before asking them to pay where possible and presenting offers clearly. Always read the current text of the guidelines before submitting.

Free: 25 Paywall Patterns from Top-Grossing Apps

The layouts, copy and offers used by the highest-earning subscription apps, annotated with why they work.

We’ll email the resource and a few practical tips. Unsubscribe in one click. We never sell your data.

Patterns that top apps use

Studying the top-grossing apps reveals recurring paywall patterns:

  1. Outcome headline. "Speak Spanish with confidence" rather than "Unlock Premium".
  2. Feature list as benefits. Three to five short lines, each starting with a verb.
  3. Two or three plans. Usually weekly or monthly and annual, with the annual plan preselected.
  4. Visible savings. "Save 40%" on the annual plan, calculated honestly.
  5. Trial timeline. A simple diagram: today you start free, a reminder before the trial ends, then billing.
  6. Social proof. Ratings or a real testimonial, with permission.
  7. Easy exit. A visible close button or "Continue with free".

Placement and timing

Where the paywall appears matters as much as what it says. Common placements:

  • End of onboarding. After a personalisation quiz that makes the value feel tailored. Widely used by top apps.
  • At a premium feature. When a user taps something that requires a subscription.
  • After a success. Following a first completed workout, lesson or project.
  • On a schedule. A reminder after a few days of free use in freemium apps.

Avoid showing a paywall before users understand what the app does, unless your brand is already well known.

Trial length and pricing

Trial length should match how long it takes users to experience your core value. A meditation app might need a week of daily sessions; a photo editor might show value in one edit. RevenueCat's 2026 data found trials of 17 to 32 days converted at about 42.5%, compared with 25.5% for trials of four days or less. Test a longer trial if your users need time to build a habit. Use the app revenue calculator to see how trial and conversion changes affect revenue.

Common paywall mistakes

Hiding the price. Users who cannot find the price assume the worst.

Too many plans. Choice overload reduces conversion.

Dishonest savings. Comparing against an inflated price damages trust and can breach guidelines.

No restore button. A frequent cause of rejection and support tickets.

A tiny close button. Frustrates users and can be treated as manipulative.

Feature lists without benefits. "Cloud sync" means less than "Never lose a note".

Testing your paywall

Once your paywall passes the checks, test it. Run one experiment at a time: a new headline, a longer trial, a different default plan or a new placement. Measure trial starts, trial-to-paid conversion and refunds together, not just trial starts. Muaz.io's Growth Studio runs these experiments with your approval and reports results with confidence levels.

Let Muaz.io build a compliant paywall

Muaz.io generates paywalls that pass these checks by default: clear pricing, restore purchases, terms and privacy links and auto-renewal disclosure, wired to StoreKit or RevenueCat. Paste your website or idea into the builder above to see your app's paywall on a live iPhone.

Paywall copy that works

Words matter. Strong paywall headlines describe what users will achieve, in their own language: "Sleep better in 7 nights", "Your budget, finally under control" or "Edit like a pro in minutes". The supporting lines should be benefits, not features, and the call to action should describe the next step honestly, such as "Start my free week" rather than a vague "Continue". Avoid urgency that is not real, such as fake countdown timers, which damage trust and can conflict with Apple's guidelines.

Personalised paywalls

Many top apps use the answers from onboarding to personalise the paywall. If a user said their goal is to run a 5K, the paywall can show a 5K plan; if they chose Spanish, it can show Spanish lessons. Personalisation makes the offer feel relevant and often lifts conversion. Keep it honest: the plan and price must be the same for everyone at the same moment unless you are clearly offering a discount.

Win-back and upgrade offers

The paywall is not only for new users. Lapsed subscribers can be shown a win-back offer, and free users who have been active for a while can be offered a time-limited discount. Apple supports introductory offers, promotional offers and offer codes for these situations. Use them sparingly and measure whether they bring back users who stay, not just users who take the discount and leave.

Measuring paywall performance

Track a small set of numbers for every paywall version: views, trial starts per view, trial-to-paid conversion, refunds and early cancellations. A version that increases trial starts but lowers trial-to-paid conversion may not be a win. Look at revenue per paywall view as the single summary metric, and give each experiment enough traffic to reach a clear result before you decide.

A paywall review routine

Review your paywall every quarter, and after any major change to your app or pricing. Re-run this teardown, compare your paywall with the current top apps in your category, check Apple's guidelines for updates and look at your conversion data. Small, regular improvements usually beat occasional big redesigns.

Anatomy of a high-converting paywall

Most top paywalls share a similar structure from top to bottom. A clear close button sits in a corner, visible but not dominant. A headline states the outcome in a few words. A short list of three to five benefits follows, each with an icon. Social proof, such as a rating or a real testimonial, appears next. Then the plans: two or three options, with the best value preselected, labelled and showing its saving. Below the plans, a trial timeline or reassurance explains what happens next. The primary button describes the action, such as "Start free trial". Finally, small print covers auto-renewal terms, with links to the terms of use and privacy policy and a "Restore purchases" link. Every element has a job, and nothing is decorative.

Copy patterns by category

Fitness. "Reach your goal weight with a plan built for you", with benefits about workouts, nutrition and progress tracking.

Language learning. "Speak with confidence in 3 months", with benefits about lessons, speaking practice and offline access.

Productivity. "Get your hours back", with benefits about automation, sync and unlimited projects.

Meditation and sleep. "Sleep better tonight", with benefits about stories, sounds and daily sessions.

Photo and video. "Create like a pro", with benefits about templates, exports without watermarks and premium effects.

Each pattern speaks to the outcome the user wants, then supports it with concrete benefits.

Design details that matter

Small design choices affect conversion. The preselected plan should be visually distinct, with a clear border or background. Prices should be easy to compare, with the billed amount prominent as Apple requires. The primary button should be large and high-contrast. Text should be readable at the default size and scale with Dynamic Type. The paywall should fit on screen without scrolling on common iPhones, or make it obvious that there is more below. And animations, if any, should be subtle and quick, never delaying the close button.

Paywalls for different business models

Hard paywalls ask for a trial or purchase before the core experience and work best when the value is clear from onboarding. Freemium paywalls appear when users reach a limit or a premium feature and work best when the free version builds a habit. Metered paywalls allow a number of free uses per period, common in content and AI apps. Feature-gated paywalls lock specific advanced features. Choose based on how users discover value in your app, and remember that RevenueCat's 2026 data shows a large conversion gap between hard and freemium models, so test the model, not just the design.

Onboarding that sets up the paywall

The paywall's performance depends heavily on what comes before it. Onboarding that asks a few personal questions, shows a tailored plan and delivers a quick first win makes the paywall feel like the natural next step rather than an interruption. Keep onboarding short, typically three to six screens, and make every question earn its place by personalising the experience. End with a summary of what the user will get, then the paywall. Many top apps follow exactly this sequence, and it is the default flow Muaz.io designs for subscription apps.

Reminders before trials end

A trial that ends without warning feels like a trap and leads to refunds, angry reviews and cancellations. A reminder a day or two before the trial converts builds trust. Apple's subscription system lets users manage subscriptions easily, and showing a reminder in your trial timeline, with a notification before the end, often increases long-term retention even if a few people cancel. Honest paywalls convert people who stay.

Paywall glossary

Hard paywall. A paywall that must be passed, via trial or purchase, before the core experience.

Freemium. A model with a permanent free tier and paid upgrades.

Introductory offer. A free trial or discounted price for new subscribers.

Promotional offer. A discount for existing or lapsed subscribers.

Restore purchases. A control that lets users recover purchases made on another device or before reinstalling.

StoreKit. Apple's framework for in-app purchases and subscriptions.

Accessibility on the paywall

The paywall must work for everyone. Support Dynamic Type so prices and terms remain readable at larger text sizes, label every control for VoiceOver, keep sufficient contrast for prices and small print and make the close button reachable with assistive technologies. An accessible paywall is also a clearer paywall for all users, which helps conversion.

Common questions about Apple's rules

Can I show a monthly equivalent price for an annual plan? Yes, but the actual billed amount, the annual price, must be the most prominent pricing element.

Do I need a close button? Apple expects users to be able to dismiss paywalls that are not essential to app function, and hiding the close button is a common source of complaints and review issues.

Can I require a subscription to use the app at all? Yes, hard paywalls are allowed, provided the app clearly explains what users get and follows the subscription rules.

Must I offer restore purchases? Yes, apps with in-app purchases must provide a way to restore them.

Where do I link the terms? Include links to your terms of use and privacy policy on the paywall and in your App Store metadata.

Example teardown: before and after

Imagine a habit app's first paywall. The headline says "Go Premium". There are four plans, including weekly, monthly, annual and lifetime, with the monthly plan preselected. Prices appear as monthly equivalents only. There is no restore button, the terms are not linked and the close button is a faint cross in the corner. The teardown scores it low, with Apple rule items at the top of the fix list.

After the fixes, the headline reads "Build habits that stick", with three benefits underneath. There are two plans, monthly and annual, with annual preselected and labelled "Best value, save 45%". The annual billed amount is the most prominent price, with the monthly equivalent in smaller text. A trial timeline explains the reminder before billing. "Restore purchases", "Terms" and "Privacy" links sit at the bottom, and the close button is clearly visible. The score rises sharply, and, just as important, the paywall is now honest and compliant.

How often to revisit your paywall

Paywalls are never finished. Review yours after every major feature release, every price change and every time a competitor in your category changes theirs. Run the teardown again, look at your conversion data and pick the next experiment. A steady cadence, such as one paywall test per month once you have enough traffic, usually produces better results than an occasional redesign.

Start your teardown now

Open your paywall, answer the questions above and fix the top items on the list. If you do not have an app yet, paste your idea into the builder at the top of this page and Muaz.io will design a compliant paywall from the start, tuned to your category. For the bigger picture of subscription economics, read the revenue calculator guide and the patterns on our top charts page.

Paywall testing ideas, ranked by typical impact

  1. Placement. Moving the paywall to the end of a personalised onboarding often has the largest effect.
  2. Trial length. Testing a longer trial against a short one, guided by the 2026 benchmarks.
  3. Default plan. Preselecting annual instead of monthly.
  4. Headline. Outcome-led copy versus feature-led copy.
  5. Plan count. Two plans versus three.
  6. Social proof. Adding a real rating or testimonial.
  7. Visual design. Layout and imagery changes, usually smaller effects.

Run them in order, one at a time, and keep the winners.

The honest paywall principle

The paywalls that convert best over time are the ones users trust. Be clear about the price, generous with the trial, explicit about renewal and easy to close. Users who subscribe with full information stay longer, refund less and review more kindly. That is good for revenue, good for App Review and good for your brand.

Fix the top three items today, and measure the difference next week.

Still have questions about paywall best practices? Ask the assistant inside the Muaz.io builder. It knows your project, your competitors and every source cited in this guide, and it answers in plain language.

Last reviewed Nov 6, 2026 by the Muaz.io research teamFigures are cited inline and in the sources below
FAQ

Questions about paywall teardown

Short, direct answers. Still curious? Ask in the builder; the assistant knows your project.

What is a hard paywall?

A hard paywall requires users to start a trial or subscribe before they can use the core of the app. A freemium model lets people use a free version indefinitely and upgrade later. RevenueCat's 2026 data found hard paywalls convert trials to paid at roughly five times the rate of freemium models by day 35.

What does Apple require on a subscription paywall?

Apple's guidelines require clear disclosure of what the subscription includes, its price and billing period, and auto-renewal terms. The amount that will be billed must be the most prominent pricing element. Apps must include a way to restore purchases and links to the terms of use and privacy policy.

How long should my free trial be?

RevenueCat's 2026 research found trials of 17 to 32 days converted about 70% better than trials of four days or less. The best length depends on how long users need to experience your app's value. Test it.

Where should the paywall appear?

The most effective paywalls appear right after users have experienced value or are about to access a premium feature, often at the end of onboarding. A paywall on the very first screen rarely works unless the value is already obvious.

Is this tool's score an official Apple check?

No. It is a self-assessment based on Apple's published guidelines and common conversion patterns. Apple's App Review team makes the final decision on compliance.

Can Muaz.io build a compliant paywall for me?

Yes. Muaz.io generates paywalls with restore purchases, terms and privacy links and clear pricing, wired to StoreKit, and the Growth Studio tests variations after launch.

Sources

Where our numbers come from

Third-party figures are estimates published by the sources below. Prices and rules change; check the source before you decide.

  1. Apple App Store Review Guidelines 3.1.2: Subscriptionsdeveloper.apple.com/app-store/review/guidelines/#subscriptions
  2. Apple: auto-renewable subscriptionsdeveloper.apple.com/app-store/subscriptions
  3. Apple Human Interface Guidelines: In-app purchasedeveloper.apple.com/design/human-interface-guidelines/in-app-purchase
  4. RevenueCat: State of Subscription Apps 2026www.revenuecat.com/state-of-subscription-apps
  5. Apple StoreKit documentationdeveloper.apple.com/documentation/storekit

Ready for the real thing?

Your tool results are a great start. Paste your website and Muaz.io builds the app around them.

Free researchNo credit cardYou own the codeCancel anytime
← Design
Project
Idle
Launch Center →

Screens

Live iPhone preview

Browser-rendered preview. Native-device validation runs on TestFlight.

AI chat

Voice + text
0 / 38 tests