Paywall UX Design: Show Pro Without Making Free Feel Locked

Good paywall UX design shows people what Pro would give them, in the exact moment they want it, without breaking what Free already does well. That was the brief I worked to on the ViewStats mobile app, the creator platform built by the team behind MrBeast: the app had to serve free users and paying subscribers at once, keeping premium tools "visible enough to communicate value without making the product feel locked or frustrating." In practice that means three rules. Never block the core loop. Name the Pro value by the question it answers, not the feature it unlocks. Put the upgrade where intent already exists. Below I walk through the use case as a case study: the context, the user problem, the options any freemium product faces, the decision, what the published result was, and what you can reuse on your own paywall.

The context: a data-heavy product on a small screen

ViewStats is a creator intelligence platform. I led design across web, mobile, a Chrome extension, the website, growth, AI experiences and the design system. The full story is in the ViewStats creator tools case study.

The web platform was where creators did deep research. Mobile had a different job. Creators do not always want to sit at a desktop to check performance or see what is happening in their niche. They needed something faster and lighter, to use between uploads, shoots, edits and meetings. So mobile was designed around a short list of on-the-go moments: checking channel performance, reviewing video rankings, tracking competitors, discovering opportunities, following trends, moving quickly between creator data, and accessing Pro insights.

Notice where Pro sits in that list. It is one of the moments, not a wall in front of all of them. That framing drove everything else.

The user problem: two audiences, one app

A freemium mobile app has two users who want opposite things from the same screen.

The free user wants clarity and speed. They opened the app between two tasks; they want an answer about their channel in seconds. If every second card is a lock icon, the app feels like an ad for itself and they stop opening it.

The Pro user paid for depth: deeper insights, advanced tools, faster research workflows. If the app hides those behind the same simplified layout the free user sees, they wonder what they are paying for.

The business needs a third thing: free users must regularly see enough of Pro to want it. Hide premium completely and nobody upgrades. Show it everywhere and nobody stays.

From the case study, the focus for free users was clarity, discovery and fast access to core analytics. For Pro users it was unlocking deeper insights, advanced tools and faster research workflows. The design job was making both true on one small screen.

Paywall UX design options every freemium product weighs

Before the decision, it helps to lay out the general patterns. These are not experiments we ran one by one; they are the standard options any product team weighs, and the trade-offs I think about each time.

Pattern	How it works	Good for	Risk
Hard paywall	Pay before using most of the app	Products whose value is obvious before trying	People leave before understanding the value
Feature gating	Core features free, advanced features locked	Tools with a clear basic vs expert split	Lock icons everywhere make Free feel broken
Teaser or preview	Show a partial or blurred Pro result in context	Data products where the answer itself is the value	Teasing too often feels like bait
Usage limits	Free up to a number of uses, then upgrade	Products used repeatedly in the same way	Hitting the limit mid-task feels like punishment

Most good apps mix these. The question is not which pattern, it is where each one appears and how it feels when it does.

The design decision: Pro as visible value, not a locked door

The principle we designed to was the one quoted above: premium tools visible enough to communicate value, without the product feeling locked or frustrating. The case study does not publish every screen (parts are under NDA), so here is how I turn that principle into decisions any team can apply:

Free covers the core loop. Fast access to core analytics was the stated focus for free users. Checking performance or rankings is the reason someone opens the app between two tasks, so that path should never feel blocked. Every day they open it is another chance to see Pro.

Pro shows up inside the moments, not in front of them. "Accessing Pro insights" was one of the on-the-go moments, next to tracking competitors and discovering opportunities. When a free user is already exploring an opportunity, a deeper insight is relevant. The upgrade belongs where curiosity already exists, not on launch.

Value before the ask. This is the same rule that took ViewStats channel connection from 13% to 65%+ in onboarding: show value first, ask for trust second. Paying is the biggest trust request in a product. I wrote about the onboarding version in onboarding UX best practices.

Clarity over more data. The same lesson from the ViewStats dashboard work applied here: creators wanted confidence about what to make next, not more charts. So Pro should be framed as a better answer, not as more numbers.

The result

I will only use the published outcome here. The mobile app reached 100,000+ downloads, and the product overall grew to 500,000+ users and evolved into a profitable creator platform. I cannot attribute those numbers to the paywall design alone, and I would not trust anyone who did: mobile, web, the Chrome extension that reached 200,000+ users, AI tools and growth all fed the same business.

What I can say is that the free and pro balance was a deliberate design problem with a clear principle, and that principle held across platforms.

What you can reuse on your own paywall

A checklist I would run on any freemium app, from a meditation app to a B2B dashboard:

• Write down your core loop. The one thing people come back for. If any paywall touches it, move the paywall.
• Name Pro by the question it answers. "See which videos your competitors are winning with" beats "Unlock Advanced Competitor Analytics".
• Count your lock icons. Open the free version and count them on the first three screens. If a stranger would describe the app as "mostly locked", you have a problem.
• Find the moments of intent. Where does a free user try to go one level deeper? That is where the upgrade belongs.
• Design the paid state too. A Pro user should feel the difference on the same screens, or they will cancel.
• Make the price and terms plain. Apple's Human Interface Guidelines have a full page on presenting in-app purchases; read it before designing an iOS subscription screen.

Where this advice does not apply: products where the value is obvious and immediate (a pro camera app with a clear sample, for example) can run a harder paywall without much harm. And very early products may need a simple paywall to learn whether anyone will pay at all. Balance is a growth-stage problem.

The paywall is also an interaction design problem, not only a business one. How the locked state looks, how the unlock feels, whether there is a moment of delight when someone upgrades: motion and sound can make that moment feel like a reward instead of a transaction. I explore that kind of detail in my interaction design experiments.

FAQ: paywall UX design

Where should a paywall appear in a mobile app?

At moments of intent, when the user is already trying to go deeper than Free allows, not on launch and not in the middle of the core task. A paywall on first open asks for money before the person knows what the app does.

Is a hard paywall or a freemium model better?

It depends on how quickly the value is obvious. If people understand the value from screenshots, a hard paywall can work. If the value comes from using the product over time, as with analytics, freemium with visible Pro value usually fits better.

How do I show premium features without annoying free users?

Show them in context and sparingly. Preview the answer a Pro feature would give, at the moment it is relevant, and keep the core loop free of prompts. If free users describe the app as mostly locked, cut the number of teasers.

Should free and Pro users see the same navigation?

In most cases, yes. One structure keeps the app learnable, makes upgrading feel like going deeper instead of moving to a different product, and keeps design and engineering simpler. The difference should be in depth on the same screens.

A simple next step

Open your app as a brand-new free user and try to do the one thing people come for. Count how many times you are asked to pay before you get an answer. If the number is more than zero, that is your first fix. If you want a product designer who has balanced free and paid on a product at this scale, you can work with me on your paywall UX.