-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Kithara is a modular real-time engine for music software. Its primary product direction is a professional DJ engine, while the underlying Core remains general enough to support other interactive music applications. Kithara App is the reference consumer and proving ground for the public engine.
The current product milestone is an embeddable mobile mixing engine for iOS and Android. The milestone requires playback to start as soon as playable data is available, externally supplied musical analysis, an editable transition between two host-selected tracks, and exact beat and downbeat alignment during execution.
Mobile comes first because it imposes stricter lifecycle, network, resource, latency, and packaging constraints than desktop. Proving the engine under those conditions creates a portable base for larger applications without carrying desktop-first assumptions into the public contract. A Spotify-style transition experience is the initial product reference, not the limit of the engine.
- Strategy — product layers, responsibility boundaries, design principles, and long-term ambition.
- Roadmap — ordered strategic outcomes and acceptance principles.
- Crates — crate architecture, contracts, and decision rationale.
- Kithara Development — capability and task order and status.
- Roadmap and product-direction feedback — propose workflows, priorities, and missing outcomes.
- Engine, SDK, and integration feedback — discuss public APIs, embedding, streaming, lifecycle, and platform behavior.
The Wiki owns strategy and crate contract explanations. GitHub Projects owns capability and task order and status. Discussions retain feedback and context. Issues and pull requests hold active implementation detail and evidence.