Howdy
Roku's new streaming app
Designing the content details page for Roku’s new mobile streaming app, Howdy. A core screen for exploring titles and deciding what to watch.

Bringing Howdy to mobile
Howdy is Roku’s new streaming service, launched on TV in 2025. With millions of subscribers and a growing audience, a mobile app became a business priority. Roku already had a mobile app with a different purpose, so we utilised what we knew about it to accelerate decision-making for Howdy.
Challenges & goals
Short timeframe: The design and build had to be completed in 4 months, so scoping had to be accurate and decisions made quickly.
Technical limitations: Howdy was built on the existing Roku mobile app infrastructure, so many behaviours carried over, constraining what could change.
A fresh identity: The app needed to look and feel different from the utility-focused Roku app while matching the Howdy TV experience, which meant extending the design system with new components and tokens.

The Howdy TV experience
Designing a key feature
Why was this important?
I led the design for multiple features for the new app. One of the most important features for the business was the content details page - the screen that surfaces all information about a piece of content and drives the key user actions: viewing details, playing, saving, rating and sharing.

The current Roku app - we leveraged our understanding of user behaviour for Howdy
Research
We already knew how users interact with a similar page on the Roku app. Analytics and user interviews showed that Roku app users mainly use it as a remote and to compare which service to stream from. Howdy users have a simpler goal of just wanting to watch content.
This meant that features built for comparing services were not needed for Howdy. We also used this as an opportunity to reduce complexity rather than carry over legacy patterns, making play the dominant action.

Benchmarking highlighted established patterns across similar pages
Process
The project started with a PRD from the product owner and we worked together with engineering to set the scope. The project culminated with a senior leadership review, but the path to get there involved:
Benchmarking: Content details pages are well understood across the industry, so I felt like it was important to align with these patterns to meet user expectations.
Feedback loops: I shared designs and prototypes regularly with stakeholders to ensure the experience was on track. Because of the technical limitations, it was important to have regular conversations with engineering.
Design system syncs: I needed to change certain tokens and components to achieve a fresh look and feel, and close collaboration with the design system team was essential to achieve this.
The Solution
Movies
Large artwork and bold typography set the tone immediately, while the primary action is obvious and everything else is within easy reach.
We removed functionality from the current Roku app, such as choosing how to stream the content, to reduce complexity and fit Howdy’s user goals.

TV shows
The page needed an additional row to surface episodes clearly, but otherwise it remained visually and structurally consistent with the movie experience - important for users switching between content types.

A new visual language
Beyond the screens themselves, two pieces of work contributed to the fresh visual language:
New components and styles: I worked with the design system team to add new components and variants for the icon action row and to show watch progress. This helps contribute to the fresh visual language while keeping consistency elsewhere in the system.

Colour blending: Working closely with engineering, we implemented a colour thieving algorithm that samples the dominant colours from the content artwork and applies them as a gradient in the status bar above. This makes the entire page feel more visually balanced without a jarring colour transition.

Trade-offs
Not everything went as planned, and there were some decisions that needed a compromise:
Legacy behaviour: The existing app uses a bottom sheet when the rate button is tapped - a pattern that felt clunky and dated. I explored alternatives, including a context menu, that would have provided a cleaner interaction. This was ultimately rejected as too complex to implement within scope, so we retained the bottom sheet.
Download functionality: Allowing users to download content for offline viewing was a feature we identified early as valuable, but it fell outside the scope of the initial release.
Animations and performance: The animations on the content details page didn't move beyond what existed in the Roku app, and some interactions felt slow as a result. Improving the motion design and performance was descoped due to timeline constraints.
Platform uniformity: We maintained a single consistent design across both platforms. This saved significant engineering time although at the cost of some platform specific conventions.

Not every feature was implemented, but the core experience shines through
Impact
Rated 4.7 stars on the App Store with strong user reviews.
Now used by hundreds of thousands of users on mobile.
Next project