Finished desktop app

Game Backlog

A desktop app to organize a video game library without turning leisure into a spreadsheet.

Status
Finished desktop app
Format
Electron, local use
Data
Personal library, filters, statuses
Next proof
Real screenshots + short video

Demo

Visual proof to add

The page is ready for real screenshots, a short video and, later, a simplified web demo with fake data. No fake screenshot is published in this version.

Short video

Suggested flow: open the app, show the main view, filters, game detail and status change. Target length: 45 to 60 seconds.

Commented screenshots

Slots for 4 to 6 screenshots: main board, game detail, filters, editing, statuses and possible stats.

Simplified web demo

V1.5 option: a browser version with fake data to explain the product without downloading the desktop app.

The problem

A video game library grows quickly: sales, subscriptions, games started then abandoned, 100% goals, multiplayer titles and games kept for later. The risk is not only not knowing what to launch, but losing track of what you wanted to do with each game.

Product intent

Game Backlog does not try to become a social network, a Steam clone or a cloud service. It is a personal tool: open, sort, decide, resume context. The product should help answer one simple question: “what do I actually want to play now, and why?”

What the app enables

  • Create and organize a personal game library.
  • Use statuses that match real usage: to play, playing, finished, 100%, platinum, multiplayer, paused, abandoned or long-term.
  • Filter quickly by mood, platform, status or goal type.
  • Keep personal notes to avoid returning to a game without context.
  • Turn a confusing list into a lightweight decision tool.

Why a desktop app

Electron matches the use case: a personal local tool opened when organizing a library or deciding what to play next. The project does not need to be a SaaS or store personal data online to be useful.

Intentional decisions

  • Prioritize local use over user accounts.
  • Avoid social mechanics or scoring systems that turn leisure into obligation.
  • Build a clear management interface before adding advanced features.
  • Keep public download secondary until builds, signing and distribution are clean.

What it shows

  • Ability to design and finish a complete personal tool.
  • Product thinking around a real recurring use case.
  • Management UI, filters, statuses and detail views.
  • A pragmatic desktop choice for local use.
  • Ability to present a finished project without pretending it is a SaaS.

Before V1 publication

The page still needs real assets: screenshots, short video and a possible poster. The structure is ready, but it is better not to publish fictional visuals for a project presented as finished.