About

GameLogfy is a personal game backlog tracker built because every existing tool either had too many opinions about how to organize games, or stored everything in someone else’s cloud. The goal was full ownership — my data, my backend, my rules.

Each game entry gets a status (Wishlist, Playing, Completed, Abandoned), a priority level (High, Medium, Low), platform tags, personal notes, and completion time estimates pulled from HowLongToBeat through a Golang server. Nothing talks to HowLongToBeat directly from the Flutter client.

There are four view modes for the log:

• List — games grouped by release year and month with animated headers
• Calendar — monthly navigation showing what releases when
• Added — sorted by the date you added the entry
• Custom — drag-to-reorder with order persisted to PostgreSQL

When a game isn’t in HowLongToBeat’s database, a manual entry form covers the same fields — name, status, priority, platforms, release date, notes.

Tech used

• Flutter, hooks_riverpod, fl_query (React Query pattern for server state)
• Golang HTTP server (HowLongToBeat wrapper)
• PostgreSQL (source of truth for all user data)
• Hive (client-side cache only)
• Firebase Auth + Google Sign-In
• shadcn_flutter, go_router
• cupertino_native_better (Liquid Glass on iOS 26+, automatic fallback)