B4cklog is a cross-platform game library, backlog, discovery, and community application. The project is currently in Early Alpha.
The public web app is available at https://b4cklog.rarmash.ru.
- Personal game library with backlog/status tracking, favorites, completion and mastery state.
- Playthroughs, play sessions, private notes, journal timeline, and calendar history.
- Game search, discovery, platform catalogs, detailed Game Hub pages, screenshots, trailers, series, editions, companies, and related games.
- Ratings and reviews, review likes and comments, activity feeds, notifications, profiles, followers, and following.
- Public and private custom lists with notes, ordering, reordering, discovery, and profile integration.
- Connected accounts and imports, including official Steam account linking, library synchronization, pending-match resolution, exclusions, playtime tracking, and Backloggd imports.
- English and Russian interfaces with light, dark, and system themes.
- Shared product behavior across the React web client and Flutter mobile client.
- B4cklog — superproject that pins the components and owns shared development, CI, Docker Compose, and deployment configuration.
- B4cklog-Server — Kotlin / Spring Boot backend API.
- B4cklog-Web — React / TypeScript web application.
- B4cklog-Mobile — primary Flutter mobile client for Android and iOS; the previous native Android client is retained as legacy code.
- B4cklog-Docs — product, architecture, development, deployment, and feature documentation.
- Backend: Kotlin, Spring Boot, JDK 21, PostgreSQL, Flyway, Spring Security, JWT.
- Web: React, TypeScript, Vite.
- Mobile: Flutter / Dart, targeting Android and iOS.
- Game metadata: IGDB.
- Infrastructure: Docker, Docker Compose, Caddy, GitHub Actions, GHCR.
The superproject is the easiest way to work with the full stack:
git clone --recurse-submodules https://github.com/B4cklog/B4cklog.git
cd B4cklog
cp .env.example .env
docker compose -f compose.dev.yaml up --buildComponent repositories also contain their own setup instructions. Project documentation lives in B4cklog-Docs.
B4cklog is being built as its own product while using established backlog applications such as Backloggd as a reference for expected workflows. Current work is focused on finishing and polishing the Early Alpha experience across web and mobile before the later Open Beta and 1.0 stages.