product
Goodgame is primarily for the creator and a small circle of friends who want a polished way to manage their gaming backlog. Users are players with enough games across platforms that memory and mood are no longer enough: they want to remember what they own, what they are actively playing, what they finished, what they abandoned, and what deserves attention next.
The usage context is personal and recurring. A user may open the app briefly after hearing about a game, while deciding what to play tonight, or after finishing a title and wanting to log notes, rating, playtime, and status.
Goodgame is a Goodreads-style gaming backlog tracker for Android and web. It helps users search game data, save games into a personal library, classify each game by status, track personal ratings and playtime, and discover relevant new or recommended games.
Success means the app feels like a trusted, low-friction personal library: quick enough for casual logging, structured enough to stay useful over time, and visually premium enough that maintaining the backlog feels satisfying instead of administrative.
Professional, premium, simple, and dark. The product should feel calm, intentional, and quietly high-quality, more like a private media library than a loud gaming portal.
The voice should be concise and useful. It can feel warm, but it should avoid jokes, hype, and over-explaining. Screens should make the next action obvious without turning into onboarding copy.
Goodgame should not look or feel like gamer neon/RGB, a corporate SaaS dashboard, a childish arcade interface, or a cluttered Steam clone.
Avoid overdecorated game-culture tropes: glowing gradients, cyberpunk purple, busy achievement walls, aggressive cards everywhere, and dense marketplace-style shelves. The product should also avoid sterile enterprise patterns that make personal tracking feel like work.
- Treat the library like a personal collection, not an inventory table.
- Keep the interface dark, restrained, and premium, with game artwork carrying most of the visual richness.
- Make status and next action instantly legible: browse, add, continue, finish, reorder, or remove.
- Prefer compact, repeatable controls over explanatory panels; users return often and should not have to reread the interface.
- Let RAWG data support personal memory, while personal notes, ratings, and statuses remain the reason to come back.
Aim for WCAG AA contrast and reliable touch targets across Android and web. Preserve usability for reduced-motion users, color-blind users, and keyboard or screen-reader navigation on web.
Color must not be the only indicator of status: pair semantic colors with labels, icons, or visible text. Motion should be subtle, purposeful, and safe to disable.