kyusetzu/karasu

Purpose and Runtime

Karasu is a Windows/Linux desktop anime and manga tracker centered on AniList. It is a Tauri 2 application: a Rust native backend hosts a React/TypeScript WebView frontend. The backend executable starts through src-tauri/src/main.rs and app wiring lives in src-tauri/src/lib.rs; the frontend mounts from src/app/main.tsx into src/app/App.tsx.

UI, Navigation, and Client State

The React application presents dashboard, list, discovery, local-library, settings, statistics, and year-review screens. Pages consume API wrappers and maintain UI-local state through Zustand; server/list data is managed with TanStack Query. Core paths: src/pages/Dashboard.tsx, src/pages/MediaList.tsx, src/pages/Settings.tsx, src/stores/auth.ts, src/stores/nowPlaying.ts, and src/api/queries.ts. Virtualized list rendering is concentrated in src/components/list/VirtualGrid.tsx.

Frontend–Native Boundary

The UI calls Tauri-exposed Rust commands through frontend API modules rather than directly owning persistence, auth, playback, or OS integrations. The frontend boundary includes src/api/anilist.ts, src/api/library.ts, and src/api/diagnostics.ts; backend command groups are organized in src-tauri/src/commands/auth.rs, src-tauri/src/commands/list.rs, src-tauri/src/commands/playback.rs, and src-tauri/src/commands/system.rs. This boundary is the primary control path for mutations and platform-dependent features.

AniList, Local Lists, and Synchronization

AniList authentication and GraphQL/client behavior are backend-owned, with browser-based login plus token management. List operations support connected AniList data and local-only operation, backed by SQLite; failed remote writes are retained as an offline queue for later synchronization. Key paths: src-tauri/src/anilist/auth.rs, src-tauri/src/anilist/client.rs, src-tauri/src/db.rs, src-tauri/src/commands/list.rs, and src/api/anilist.ts. Tokens use the OS credential store except in portable-mode handling at src-tauri/src/portable.rs.

Playback Detection and Scrobbling Pipeline

Detection sources produce playback candidates, which are parsed and matched to AniList media, then evaluated for progress updates and scrobbled subject to thresholds, confirmation, gap protection, and anime relations. The orchestration is under src-tauri/src/playback/mod.rs; source adapters include Windows/Linux media sessions and Jellyfin in src-tauri/src/playback/detection/media_session/mod.rs and src-tauri/src/playback/detection/jellyfin.rs. Recognition and filename/title parsing are separated in src-tauri/src/playback/recognition/matcher.rs and src-tauri/src/playback/recognition/parser.rs; writes flow through src-tauri/src/playback/scrobbler.rs.

Native Services and Integrations

Rust owns desktop-specific behavior: system tray/window lifecycle, notifications, local filesystem library scanning/matching, Discord Rich Presence, diagnostics, logging, and update checks. Architectural modules are src-tauri/src/library.rs, src-tauri/src/alerts/mod.rs, src-tauri/src/discord.rs, src-tauri/src/diagnostics.rs, and src-tauri/src/commands/update.rs. External services are AniList, optional Jellyfin /Sessions, Discord, and OS media APIs: SMTC on Windows and MPRIS on Linux.

Build and Distribution

Vite builds the frontend while Tauri packages native installers/AppImages. Tauri capabilities and application settings are declared at src-tauri/capabilities/default.json and src-tauri/tauri.conf.json; Rust dependencies/build settings are in src-tauri/Cargo.toml. Release automation produces update artifacts via scripts/release/generate-update-manifest.ps1; CI/release workflows are .github/workflows/ci.yml and .github/workflows/release.yml.