WhatShouldIPlay

WhatShouldIPlay is an open source game-picker platform with:

• A GitHub Pages web app for spinning a wheel from live top-game sources and user-entered games
• A Rust + Dioxus desktop app with local game scanning and the same spin experience
• Automated data refresh and deployment workflows

Live site:

• https://optimumaf.github.io/WhatShouldIPlay/

Features

• Multi-source pool support:
  • SteamCharts
  • SteamDB (with Steam charts API fallback)
  • TwitchMetrics
  • itch.io top rated
  • Manual game entry
  • Desktop-only local scan (Steam manifests + Epic manifests + common Epic/GOG/Ubisoft/Xbox install folders)
• Mode presets (Balanced Mix, Quick Pick, No Repeats, Owned Focus)
• Weighted wheel odds with per-source weighting controls
• Spin history + configurable cooldown to reduce immediate repeats
• Advanced filters (platform, tags, estimated length, release window, price)
• Steam account import using Steam Web API key + SteamID64
• Source-mix random wheel spin with animated result
• Winner popup celebration overlay with odds + source details in both web and desktop apps
• Optional cloud sync across devices via user-provided private GitHub Gist
• Progressive Web App support (installable web app + offline shell cache)
• Optional web notifications for trend updates and spin reminders
• Multi-language web UI support (English and Spanish)
• Scheduled data refresh and deterministic static hosting

Technology

• Web UI: React 19, TypeScript 5, Vite 7, TanStack Query, Zod
• Data ingestion: Node.js + Cheerio
• Desktop: Rust + Dioxus 0.7 + Reqwest + Scraper
• CI/CD: GitHub Actions + GitHub Pages

Repository Layout

.
├─ src/                      # Web app source
├─ public/data/              # Generated source dataset consumed by web app
├─ scripts/                  # Data ingestion/updater scripts
├─ apps/desktop/             # Rust + Dioxus desktop app
├─ .github/workflows/        # CI/CD automation
└─ docs/                     # Contributor and architecture documentation

Getting Started

Prerequisites

• Node.js 20+
• npm 10+
• Rust toolchain (for desktop app only)

Web App

npm install
npm run fetch:data
npm run dev

Build for production:

npm run build:all

Desktop App

cd apps/desktop
cargo run

Enable optional shortcut crawling scan:

cd apps/desktop
cargo run --features deep-shortcut-scan

Configure Windows code-signing secrets for CI (requires a .pfx code-signing cert):

.\scripts\set-windows-signing-secrets.ps1 -CertPath "C:\path\codesign.pfx" -CertPassword "your-password"

Release build:

cd apps/desktop
cargo build --release

NPM Scripts

• npm run dev: Start local web development server
• npm run typecheck: TypeScript type checking
• npm run build: Build web app
• npm run fetch:data: Refresh source data JSON
• npm run build:all: Refresh data and build web app
• npm run ci:web: Run web CI checks locally

Automation

• refresh-data.yml: Scheduled source data refresh every 6 hours
• deploy-pages.yml: Web build and Pages deploy on master
• build-desktop.yml: Windows/macOS/Linux desktop artifact builds on push/PR to master
• package-desktop.yml: Native desktop package build on version tags (v*) and manual runs, with packaged artifacts published to GitHub Releases on tags
• release-desktop-signed.yml: Enforced Windows signed release pipeline on version tags (v*)
• web-ci.yml: Web quality checks on push/PR

Data Source Caveats

• SteamDB can block non-browser traffic via Cloudflare.
• The updater attempts direct SteamDB parsing first, then falls back to Steam charts API to maintain continuity.
• Browser environments cannot scan installed local games; local scan is desktop-only.

Open Source Standards

• License: MIT
• Contributor Covenant code of conduct
• Standard issue and pull request templates
• Security disclosure policy
• Governance and support docs

See:

• CONTRIBUTING.md
• CODE_OF_CONDUCT.md
• SECURITY.md
• SUPPORT.md
• GOVERNANCE.md
• docs/ARCHITECTURE.md
• docs/desktop-ui-strategy.md
• docs/component-system.md
• docs/DEVELOPMENT.md
• docs/RELEASING.md
• docs/feedback-loop.md