A web application for organizing, exploring, and sharing board game collections.
VIEW WEBSITE ↗︎Live product
Board & Chill started from a simple real-world situation: managing a growing board game collection. Collections become difficult to navigate when games differ by player count, category, complexity, and preference.
What should we play tonight?
I wanted the application to do more than behave like a spreadsheet with game covers. It needed to make a collection useful, supporting both organization and discovery without turning maintenance into another chore.
How might we make a board game collection easier to manage while also helping people quickly decide what to play?
I designed and developed the product end to end, using it to explore both product and engineering decisions.
My first instinct was to focus on CRUD operations. Adding, editing, and deleting games were necessary, but they were not the real value of the product.
Once the games are in the application, the collection should help the user do something with them. Search, filtering, public collections, and game-night discovery became as important as maintenance.
The product was organized around a small set of core activities.
Browse and manage the games in a personal collection.
Discover games through categories, tags, and relevant attributes.
Separate games of interest from games already owned.
Share a collection through a username without exposing private account functionality.
Narrow a collection using practical criteria and decide what to play faster.
Board game libraries are highly visual, so the interface uses cards and strong hierarchy instead of dense tables. Each card exposes enough information for a quick decision without overloading the interface.
Actions remain consistently positioned, while search and filtering prevent navigation from becoming inefficient as a collection grows.
The authenticated owner needs management tools, while a visitor only needs to explore. I treated public profiles as their own browsing experience instead of exposing editing controls everywhere and hiding them conditionally.
This created a cleaner visitor experience and clearer ownership boundaries.
I tested the application throughout development to see whether it remained understandable as more functionality was introduced.
Board & Chill uses Nuxt and a reusable component-based interface. Supabase provides authentication and persistent data, and the frontend is deployed through Vercel.
Moving beyond the prototype meant designing states that static mockups often miss.
The final application connects collection management with game discovery. Users can maintain a library, organize games, manage a wishlist, and share their collection publicly.
CRUD functionality was necessary, but it was not the product’s main value.
More games made information density and filtering significantly more important.
Managing a collection and casually browsing it are two different experiences.
Authentication, responsive states, and connected data exposed problems that static mockups could not.
Screens from the product, covering its main flows and interface details.