initial commit
This commit is contained in:
commit
b811d93560
12 files changed
+952
No files matched your search
@@ -0,0 +1,69 @@
|
||||
# Product Brief
|
||||
|
||||
## Name
|
||||
|
||||
The official app name is Steam Backlog Helper.
|
||||
|
||||
Use neutral technical identifiers where possible:
|
||||
|
||||
- Repository name: `steam-backlog-helper`
|
||||
- Package ID: `com.boris.backloghelper`
|
||||
- Internal slug: `backlog-helper`
|
||||
|
||||
## Purpose
|
||||
|
||||
Build a cross-platform desktop app that helps a Steam user pick a game from a large backlog.
|
||||
|
||||
The app should reduce decision fatigue by combining Steam library data, public metadata, completion-time estimates, review signals, and a short set of user answers.
|
||||
|
||||
## Target User
|
||||
|
||||
The initial user is a Steam user with a large library and many unplayed or lightly played games.
|
||||
|
||||
Secondary users may include:
|
||||
|
||||
- Players trying to finish owned games before buying more.
|
||||
- Players who want recommendations based on time available.
|
||||
- Players who want to rediscover forgotten purchases.
|
||||
- Players who want a randomizer with more context than pure chance.
|
||||
|
||||
## Core Problem
|
||||
|
||||
Steam libraries often contain many owned, unplayed, partially played, or forgotten games. Steam itself exposes library and playtime data, but it does not provide a focused workflow for choosing what to play next based on the user's current situation.
|
||||
|
||||
## Product Principles
|
||||
|
||||
- Fast decision-making over exhaustive catalog management.
|
||||
- Recommendations should be explainable.
|
||||
- The user should answer only a short set of questions before receiving useful options.
|
||||
- True random should remain available as a toggle.
|
||||
- Local-first storage is required for the first version.
|
||||
- Small app size matters more than fastest possible development.
|
||||
- The app should support Steam launch links for selected games.
|
||||
|
||||
## Initial Success Criteria
|
||||
|
||||
- The user can enter a Steam profile and Steam Web API key during setup.
|
||||
- The app imports owned Steam games for public or API-accessible libraries.
|
||||
- The app excludes demos, tools, soundtracks, and DLC by default while keeping free-to-play games.
|
||||
- The app asks short recommendation questions covering time available, genre preference, completion preference, review-score tolerance, and randomness.
|
||||
- The app presents a short dynamic list of games to play now.
|
||||
- The app includes a slot-machine style picker animation.
|
||||
- The app can open selected games through Steam app ID launch links.
|
||||
- The app runs on macOS, Windows, and Linux.
|
||||
|
||||
## Non-Goals For The First Version
|
||||
|
||||
- Replacing Steam as a launcher.
|
||||
- Full library management.
|
||||
- Manual metadata editing.
|
||||
- Private-profile fallback imports.
|
||||
- Installed-game detection.
|
||||
- Recommendation history.
|
||||
- Import/export.
|
||||
- Mood tagging.
|
||||
- Social recommendations.
|
||||
- Multiplayer matchmaking.
|
||||
- Full achievement tracking dashboards.
|
||||
- Cloud account infrastructure.
|
||||
- Mobile app support.
|
||||
Reference in new issue
Block a user