Chrome Extension UX Design: How Ours Reached 200,000+ Users

Good Chrome extension UX design starts with one decision: bring the value to the page the user is already on, instead of asking them to come to you. That is the whole lesson of the ViewStats Chrome extension, which I worked on as Lead Product Designer and Design Engineer for the creator platform built by the team behind MrBeast. Creators lived inside YouTube. So instead of sending them to another dashboard, the extension surfaced channel and video intelligence directly inside YouTube. It grew to more than 200,000 users and became a major acquisition and retention channel. This post walks through that decision as a use case: the context, the user problem, the design challenge, the result, and what you can reuse for your own extension.

The context: a creator platform competing with YouTube for attention

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

The research behind the product came from creator interviews, onboarding analytics, Discord community feedback, support requests and internal workshops. One insight shaped almost everything: creators were not asking for more charts. They wanted confidence about a simple question, "What should I make next?"

That matters for an extension, because confidence is needed at the moment of research, and the moment of research happens on YouTube. A creator looks at a competitor's video, wonders why it took off, and wants an answer right there. Every new tab between the question and the answer is a chance to give up.

The user problem: tab switching kills research

The web app was powerful, but it lived somewhere else. To use it, a creator had to leave the video they were looking at, open ViewStats, search for the same channel or video, and then switch back. Do that ten times in a research session and the tool starts to feel like work.

So the problem was not "we need more features in the extension." The problem was location. The insight had to meet creators where they already were, which is a very different brief from "build a mini version of the dashboard."

I have seen the same pattern in other products. At Greenely, an energy app used by more than 200,000 households in Sweden, a lot of the design work was about getting price signals in front of people at the moment they could act on them. The data was never the hard part. The timing and the place were.

Chrome extension UX design: the core challenge was utility vs simplicity

The case study names the design challenge in four words: balancing utility with simplicity. The extension had to surface powerful information without disrupting the YouTube experience. That tension is the heart of Chrome extension UX design, because you are a guest on someone else's page.

The feature set that shipped was not small. It included Views Over Time, Video Performance Analysis, Thumbnail and Title Change History, Channel Insights, Trending Channels, Video Comparison Tools, Ranking Systems and One-Click Analytics. Putting all of that on top of YouTube without making YouTube worse is the actual job.

Here is how I think about that balance, and what I would tell any team designing an extension:

• The host page wins. The user came for YouTube, not for you. Anything you add has to feel like it belongs there, and has to stay out of the way when it is not needed.
• One glance, then depth. The first thing a creator sees should answer the question they had, in a single look. Deeper analysis can be one click away, not on screen by default.
• Context decides content. On a video page, show video insight. On a channel page, show channel insight. The page already tells you what the user is thinking about.
• Consistency with the main product. The extension used the same design system as the web app, mobile app and marketing site. When a creator moves from the extension to the dashboard, nothing should feel foreign.

Choosing where your extension lives on screen

Chrome gives you several UI surfaces, and the surface you pick changes the whole experience. The official Chrome extension UI documentation lists them: actions and popups, side panels, context menus, keyboard commands, badges, notifications, override pages and more. Here is how I would match them to jobs.

Surface	Good for	Weak for	Design risk
Content injected into the host page	Insight right next to the thing it describes, at a glance	Long workflows, heavy settings	Breaking or cluttering the host layout
Side panel	Deeper analysis that stays open while browsing	Quick one-number answers	Competes for screen width
Popup from the toolbar icon	Quick actions, account state, settings	Anything tied to what is on the page	Hidden, so users forget it exists
Badge on the icon	Signalling that something new or relevant exists	Explaining anything	Noise if it is always lit
Context menu or keyboard command	Power users and repeated actions	Discovery by new users	Invisible to most people

Most good extensions combine two or three of these. The mistake I see most is putting everything in the popup, because it is the easiest surface to build. It is also the furthest from the page the user is looking at.

The result: 200,000+ users and a growth channel

The extension grew to more than 200,000 users. It became a major acquisition and retention channel and one of the most valuable touchpoints in the whole ViewStats ecosystem, alongside a platform that reached 500,000+ users and 100,000+ mobile downloads.

The acquisition part is worth pausing on. An extension that is useful on YouTube gets seen and talked about by people who are already on YouTube. Every insight shown on a video page is a small demo of the full product. That is a very different growth loop from paid ads pointing at a landing page.

The retention part comes from the same place. A creator does not need to remember to open ViewStats. ViewStats is already there when they do their normal research. The same principle drove the onboarding work that took channel connection from 13% to 65%+: show value first, ask for trust second. I broke that one down in my post on onboarding UX best practices.

What you can reuse for your own extension

If you are designing a Chrome extension for a product that already has a web app, here is the checklist I would start with:

• Write down the exact moment on the host site when your user has a question. Design for that moment first.
• Answer that question in one glance, on the page. Put depth one click away.
• Pick surfaces deliberately. Do not default to the popup.
• Use the same design system as your main product, so the extension feels like the same company.
• Treat the extension as a growth channel from day one: measure installs, active use and how many users move from the extension to the main product.
• Read the Chrome Web Store best practices before you write your listing. The store page is part of the UX.

Where this advice does not apply: if your extension is a pure utility with no host page to live on, like a tab manager, the "meet users where they are" logic shifts to the browser itself, and the popup or new-tab override may be the right home.

I also believe interfaces should feel alive, and an extension is no exception. If you want to see how I approach motion and interaction in small surfaces, my AI design experiments are all working builds rather than mockups.

FAQ: Chrome extension UX design

What makes good Chrome extension UX design?

It respects the host page, answers the user's question at the moment they have it, and keeps depth one click away. The best extensions feel like a natural part of the site they sit on, not a second product fighting for attention.

Should a Chrome extension copy the main web app?

No. It should share the design system and the data, but not the layout. The web app is where people go to work. The extension is where the work comes to them. Trying to fit a full dashboard into an extension usually makes both worse.

Can a Chrome extension drive user acquisition?

Yes. At ViewStats the extension became a major acquisition and retention channel with more than 200,000 users. Every useful insight shown on a page the user already visits works as a small demo of your product.

Which Chrome extension surface should I start with?

Start with the surface closest to the user's question. For page-specific insight, that usually means content on the page or a side panel. Use the popup for settings and account state, not for your core value.

Need help designing your extension?

If you are planning a Chrome extension or trying to grow one that people install and forget, I would be glad to look at it. You can work with me as your product designer, or browse my product design work first.