How jpochyla/psst works
Project type and purpose
• Psst is a native desktop Spotify client written in Rust. It comprises:
• A core library (psst-core) handling Spotify sessions, audio retrieval/decoding/output, caching, queueing.
• A GUI app (psst-gui) built on Druid.
• A CLI example (psst-cli).
• A protocol crate (psst-protocol) containing Protobuf definitions and generated Rust code for Spotify’s APIs (authentication, metadata, playlists, Mercury, etc.).
File structure
• Top‐level crates:
• psst-protocol – Protobuf definitions → Rust modules
• psst-core – Core functionality: session, connection, audio pipeline, cache, playback queue
• psst-gui – UI layers: controllers, data models, view widgets, WebAPI client
• psst-cli – Minimal command‐line front end
• Packaging and CI:
• .github/workflows/build.yml – CI build & release
• .homebrew, .pkg – Homebrew formula and AppImage/Debian packaging
• Config & metadata:
• Cargo.toml / Cross.toml – Build definitions
• README.md – Project overview and build instructions
README for insights
• Confirms architecture: core + GUI + CLI + protocol.
• Lists dependencies: Rust stable, Druid (GTK/X11/Wayland), audio backends (CPAL/Cubeb), HTTPS for CDN.
• Describes features: playback, search, caching, queue, theming.
Final advice
• Every crate and its role.
• Layers (UI → business logic → network → storage/output).
• Do not overcomplicate: break into as many labeled components as necessary to reflect the modular Rust workspace.