Context

I wanted to explore what a dedicated app for Snow League fans could do. The starting point was five questions: What is this? When is it on? Where do I watch? Who’s winning? Who should I follow?

This was an independent weekend prototype, not a commissioned project or an official league engagement.

Design around the fan’s time

I reviewed more than twenty sports apps and the league’s public information to define the core fan tasks. The prototype puts the fan’s local time first, with venue time alongside it. A countdown and reminder sit beside the broadcaster handoff.

The app points viewers to the broadcaster instead of trying to replace it. Event discovery, preparation, and following the competition form the experience around watching.

Build enough to test the experience

I assembled a 78-athlete dataset from public league pages and used it for the roster and standings. A simulated tournament let me build the transitions between upcoming, active, and completed matches without depending on a live event.

The prototype labels its scores as simulated. That distinction matters: it demonstrates the interaction, not a connection to official live results.

What remains to be learned

The build turned the product idea into something people could use and critique. It also made the unresolved questions concrete: access to official event results, the production data model, and what fans and the league would actually need.

The fan tasks are still assumptions to validate. A working prototype and a product requirements document are the output of this project; a launched app and measured fan outcomes are not.

My role

I handled the research, product requirements, interface design, and implementation. The prototype uses Expo, React Native, and TypeScript to share the experience across iOS, Android, and web.