Context
BoardGameGeek (BGG) is the IMDb of board games — a massive database with community ratings, forums, collection tracking, and play logging. It's the platform serious board gamers live on. But the official app reflects the complexity of the site: overwhelming, cluttered, trying to do everything at once.
Gametrove is a focused companion app that connects to your existing BGG account and presents a stripped-down, visually-driven experience for the things collectors actually do most: admire their collection, log plays, and track stats.
Problem framing
BGG's app is comprehensive but exhausting. It carries the full weight of a feature-rich website into a mobile experience — forums, wishlists, marketplace, community features — none of which belong in a focused mobile tool.
The core opportunity: a large, engaged community of people who already have their data in BGG and want a better way to interact with it on mobile. Not a replacement — a better interface for the parts that matter most.
My role
Solo project from concept to App Store. No backend — Gametrove reads directly from BGG's existing API using the user's BGG username. I owned all design and product decisions. As my first shipped app, this was also a deliberate exploration of how far AI-assisted development could take a solo non-developer.
Key design decisions
Box art as the primary UI element
I chose large, prominent box art as the dominant visual treatment — full-width images in the collection grid and a hero image on every game detail page.
Board game box art isn't decoration — it's how collectors identify and emotionally connect with their games. The physical shelf experience is visual first. Most digital implementations reduce games to text lists with small thumbnails, which strips out what makes a collection feel like a collection. I wanted the app to feel like walking into a well-stocked game store, not browsing a spreadsheet.
No account creation — BGG username as identity
I chose to skip building a user backend entirely. Users enter their existing BoardGameGeek username and their data loads directly from BGG's API.
Asking someone to create a new account to access data they already have elsewhere is unnecessary friction. BGG is the source of truth — Gametrove is just a better interface for it. Zero sign-up also means zero barrier to first value.
Minimal play log — most fields optional
I chose to strip the play log down to the bare minimum, with most fields optional.
BGG's log form asks for too much. The friction of a long form is exactly why people don't log consistently. If logging a game takes 30 seconds, people do it. If it takes 3 minutes, they don't. I kept only what's genuinely useful and made almost everything optional.
Monthly stats alongside all-time
I chose to show both monthly and all-time stats rather than all-time only.
Annual Wrapped-style stats work for Spotify because people listen daily. Board gamers might play once a week. Monthly stats create a tighter feedback loop that rewards consistent logging and gives people a reason to open the app regularly — not just once a year.
Outcome
Gametrove is live on iOS. As my first shipped app, the primary outcome was proof of concept: a solo non-developer can design, build, and publish a polished consumer app using AI-assisted development. That question is now answered.
Reflection
Gametrove was as much an exploration of what's possible with AI-assisted development as it was a product. I wanted to understand how far a single person without deep coding knowledge could go — and the answer was further than I expected.
What I'd do differently: talk to the community earlier and more deeply. I did some desk research on BoardGameGeek forums and board game subreddits, but I leaned more on my own instincts than on real user input. The BGG community is tight-knit and opinionated — genuine discovery conversations before building would have sharpened the feature decisions considerably.
The bigger lesson carried forward into Recipe Fox: understand the distribution problem before you solve the product problem.