Selected work

From workstation analysis to a mobile pulse-check.

I helped build Viewstats on the web, then led its first iOS app as Design Lead. The challenge was to turn dense analytics into a quick, useful check-in—not just put a dashboard on a smaller screen.

This case study contains limited visuals due to an NDA.

MY ROLEDesign Lead
WHEN2023–2025
FOCUS0 → 1 · MOBILE & SAAS
Viewstats product interface designed by Anthony Myrick-Lawson

The web platform hit 500k creators. But creators don’t live at their desks.

As Founding UX Designer, I built the Viewstats web platform from scratch with one other designer: detailed dashboards for tracking channel performance, comparing videos, and spotting ways to grow.

It reached 500k+ creators in about six months. That number belongs to the web product, not the iOS app that came later.

Then I stepped into the Design Lead role and led the iOS app. The question wasn’t how to shrink the dashboards. It was what a creator actually needs when they pull out their phone between uploads.

And then we saw the trap: a raw view count doesn’t tell a creator if they’re winning.

At a desk, creators had time to filter, compare, and figure out what the numbers meant. On a phone, they have seconds. A view count on its own just raises more questions: Is that good? Better than last week? Better than channels like mine?

So I set one rule for the app: no number stands alone. Every stat ships with its comparison built in, and the deeper detail stays one tap away. That rule guided every decision across 40+ views.

Desktop-style analysis asks creators to filter and compare before they can tell how they’re doing.

Show performance with its comparison built in, then let creators choose when to dig deeper.

So instead of copying YouTube Studio, I looked at how Robinhood and other finance apps answer “Am I up or down?”

There weren’t many good mobile YouTube analytics apps to learn from, so I pushed the team to look elsewhere. Investing apps like Robinhood and Public answer the same question creators have—how am I doing, compared to what?—in a few seconds on a small screen.

We borrowed how they work, not how they look: small trend lines that show direction at a glance, up/down badges that say exactly what you’re being compared to, and cards that show the headline first with the detail underneath.

  • Small trend lines show direction without opening a full chart.
  • ±24h badges answer “compared to when?”
  • Cards let creators scan first and dig in only when they want to.

Then we locked down the 4 anchor screens before touching the other 36 views.

I built the design system off the four screens creators open most: Home, Top Lists, Favorites, and My Profile. If the quick-read approach worked there, it would work everywhere.

Locking down layout, spacing, cards, type, and up/down colors on those screens gave designers and engineers one shared language for 40+ views. The heavier analytics screens could then reuse what already worked instead of starting over.

Home: search and discovery

One clear starting point: find a channel fast, or browse categories if you don’t have one in mind.

Top Lists: browse rankings

Rankings give every number context. Where a channel stands often says more than the count itself.

Favorites: followed channels

The channels a creator keeps checking—their own and their competitors’—in one list.

My Profile: account navigation

The same system carried into settings, so the whole app feels consistent.

To handle dense analytics, we led with the pulse and tucked the heavy math behind tabs.

Channel Overview and Video Detail hold the most data: view and subscriber trends, similar channels, engagement, A/B tests, and title changes. Showing it all at once would just bring the desktop problem to a smaller screen.

So each screen leads with how things are going, and tabs and cards hold the comparisons and history underneath. Creators can go from a quick look to real analysis without losing their place.

Channel Overview

Lead with how the channel is doing, then use tabs for videos, similar channels, and about info.

Video Detail and Change Gallery

Put performance and changes side by side, so a creator can see whether a new title or thumbnail actually moved the numbers.

I killed manual search: I designed live rankings right onto the channel page.

Before, if you wanted to know where a channel ranked, you had to leave it, open the Top Lists tab, and scroll through leaderboards to find it.

For the iOS app, I pitched and designed Current Top Lists. Open any channel, and its page shows every top list that channel currently sits on. The answer to “where do they stand?” is there the second you land, no hunting required.

It was built for the app. When I left, the desktop product didn’t have it.

Leading the team meant staying in Figma, not just handing off direction.

I wasn’t just setting direction and handing things off. I was leading the team and designing every day.

Mentoring designers

I ran daily critiques with two designers, using the design system and the “no number stands alone” rule as our shared reference.

Working with engineering

I owned the relationship with engineering from specs through QA, so what got built matched what we designed.

Weekly priorities with the PM

Each week I set priorities with our PM, weighing what was doable against what mattered most to creators.

Getting iOS right

I worked closely with our iOS developers on Apple’s design guidelines and the details that make an app feel native.

Web traction first. Then a native app built around context.

As Founding UX Designer, I helped build the web platform that reached 500k+ creators in about six months.

As Design Lead, I shaped the iOS app from zero: its structure, its design system, and a simpler way to read dense analytics across 40+ views, including Current Top Lists. I designed key flows myself, ran design reviews, and worked with engineering on specs and QA. I left before the app launched; the designs shown are from April 2025, and the App Store image shows the app as it was later released.

Mobile isn’t a smaller dashboard. It’s a different question.

The biggest lesson: design for the moment, not the data. Once we agreed the phone should answer “how am I doing right now?”, it got much easier to decide what to show, what to hide, and what to build next—and to explain those calls to product and engineering.

Astray

View case study