Platform design · Vimeo · 2016–2025

Building the platform
that lets anyone
run a streaming channel.

A 9-year journey designing Vimeo Streaming's cross-platform distribution suite — from the initial post-acquisition integration of VHX to a mature product serving creators on web, mobile, and every major TV platform.

$429M+
Annual creator revenue
Millions+
Daily plays
11
Platforms (web, mobile, TV)
5,000+
Channels launched

Two sides of one
very hard platform.

Vimeo Streaming had to serve two fundamentally different users simultaneously — each with conflicting needs — on a single product surface.

The creator

  • Needs full brand control — their channel, their identity
  • Wants to manage subscribers, pricing, and content in one place
  • Has no engineering team — needs no-code app publishing
  • Expects analytics to understand what's working
  • Must comply with platform guidelines (Apple, Roku, Google)

The viewer

  • Expects a native, platform-appropriate experience
  • Won't tolerate generic-looking apps that feel "built by template"
  • Moves between web, phone, and TV — expects continuity
  • Pays the creator directly — trust is the product
  • Discovers content differently on each platform

Three directions.
One clear winner.

Before committing to an architecture, I explored three fundamentally different models for how creators would customize and publish their apps.

01

Full granular control

Every element — colors, layout, typography, section order — fully editable. Maximum creator flexibility, matched by maximum complexity.

✕ Rejected — Cognitive overload
02

Single locked theme

One beautiful default. Creator only sets their logo, colors, and content. Fastest time-to-launch, least differentiation across channels.

✕ Rejected — Brand dilution
03

Modular template system

Curated, platform-compliant templates with guided customization zones. Structure ensures compliance; flexibility enables brand expression.

✓ Shipped

The constraints that
shaped the decision.

Platform compliance wasn't optional — Apple, Roku, and Fire TV all have strict HIG requirements. Any solution had to make compliance invisible to creators while still feeling like their brand.

Consideration Full control Locked theme Modular templates
Platform compliance Creator's problem Guaranteed Built-in by design
Brand differentiation Maximum None Meaningful within guardrails
Time to launch Weeks of setup Hours Days — right amount of effort
Support burden Extremely high Minimal Low — decisions are guided
Viewer experience Unpredictable Consistent but bland Consistently excellent
"The real insight was that creators don't want infinite options — they want confidence. A well-designed constraint gives them that."

One product. Three
platform realities.

The modular App Builder shipped across web, mobile, and TV — each platform treated as a first-class citizen with its own interaction patterns, navigation paradigms, and visual hierarchy.

💻

Web

The creator's primary management surface. Drag-and-drop layout, inline preview, instant publishing. Designed to be usable by non-technical creators with zero onboarding.

Creator-facing
📱

Mobile (iOS + Android)

Viewer-first experience with creator-branded splash screens, subscription flows, and offline download. Designed around the moments between episodes, not just playback.

Viewer-facing
📺

TV (tvOS, Android TV, Roku, +more)

10-foot UI adapted per platform HIG. Focused on content discovery and lean-back browsing. Navigation designed for remotes — no hover states, no text input assumptions.

Viewer-facing

The product,
in detail.

A look at the shipped interfaces across the Vimeo Streaming platform.

Vimeo screen 1
Vimeo screen 2
Vimeo screen 3
Vimeo screen 4
Vimeo screen 5

What shipped. What I
learned. What I'd do
differently.

6+
TV and mobile platforms with consistent creator-branded experiences
0→1
App Builder built from scratch — became the primary creator acquisition driver
9yr
Tenure on the product — through VHX acquisition, rebrand, and platform shift to B2B
M+
Daily video plays through creator-published apps on the platform

What worked

The template system gave creators enough flexibility to feel ownership without opening support chaos. Compliance-by-default was the right call.

What I'd do differently

We should have invested in viewer-side research earlier. Creator feedback dominated the roadmap because they were vocal — viewers were invisible until churn data surfaced the signal.

Hardest constraint

Platform app store reviews move slowly and reject unpredictably. Designing for compliance meant building UX guardrails that creators sometimes resented — that tension never fully resolved.

What I'm proud of

The TV app design held up for years without major rework. Designing for the 10-foot paradigm early — when it wasn't mainstream — meant the architecture was solid when streaming exploded.