PlayoffBlitz had an established desktop product but no dedicated mobile experience. My role was to translate the existing feature set and visual identity into an app that could work naturally on a phone.
I led the mobile design from information architecture through high-fidelity prototyping, designing 20+ screens, building reusable components, and testing key interactions with Figma Make.
Mobile screens designed
Interactive prototype flows
Reusable component system
Mobile UX/UI ownership
The desktop product relies on dense tables, player stats, and league information. The challenge was deciding what to prioritize, what could be simplified, and how to keep frequent actions fast on mobile.
I mapped the app's navigation and screen relationships first, then used low-fidelity wireframes to test hierarchy and layout before moving into polished UI.
The final mobile experience focused on three primary areas: setting lineups, checking player data, and viewing standings. Each section was designed to keep key information accessible without overwhelming the smaller screen.
After establishing the UI, I used Figma Make to build and test high-fidelity interactions. I prompted specific behaviors one at a time, reviewed the results, and refined them to match the intended experience.
Figma Make did more than speed up prototyping. Testing real interactions surfaced usability issues like duplicate selections, unclear completion states, and missing functions before the prototype was finished.
I built a reusable component system for navigation, filters, player data, tables, and repeated interaction states. Shared patterns helped keep the experience consistent across 20+ screens and made updates easier as the prototype evolved.
I carried the existing PlayoffBlitz identity into the app through typography, color, iconography, and interface patterns so the mobile experience felt connected to the website.
The final prototype translated PlayoffBlitz's core fantasy football experience into a focused mobile product with clear navigation, reusable components, and realistic interactions across the app's main flows.
Designing for a smaller screen reinforced the importance of prioritizing the information and actions users need most. Prototyping real interactions also helped surface usability issues that static screens alone would not have revealed.