GAME TRACKER.
A personal game tracking application built with Python.
Why it exists.
GameTracker started as a way to practice core Python while solving a real, everyday problem: keeping track of which games I'm playing, which ones are finished, and which ones are still sitting in the backlog.
Instead of a tutorial project, I built something I'd actually use: a command-line tool that lets me add games, update their status, and keep that list saved between sessions. It's simple by design: the goal was to get the fundamentals right before adding complexity.
The project touches on data structures, file I/O, and basic program architecture: the concepts a CLI tool needs to feel solid rather than fragile.
Why start with a CLI?
A terminal interface keeps the first version focused on the data: adding entries, editing them, and saving the library between sessions. JSON provides persistence without introducing a database, keeping file handling and the core application flow at the center of the project.
See it run.
Select Show all to read the complete simulated session.
What it does.
- 01Add games: register a new title with its current status
- 02List games: view the full library at a glance
- 03Change status: update where each game sits in your library
- 04Edit games: update details on an existing entry
- 05Remove games: delete a title from the library
- 06JSON persistence: the library survives between sessions
Development process.
- 01Basic Python structure
- 02Terminal menu
- 03Add and list games
- 04JSON persistence
- 05Status management
- 06Edit / remove system
EXPLORE THE CODE.
VIEW ON GITHUB →GameTracker is a small project, and it's meant to be. The point was never to build something impressive on day one, but to build something real while the fundamentals were still being learned. The next version will likely move past the terminal, but the habit it built (shipping something working, then improving it) is the part that carries forward into whatever comes next.