Keyclack

Keyclack’s core asset pipeline centers on a high‑fidelity audio sprite (sound.ogg) that consolidates 50+ individual keypress recordings into a single OGG file, dramatically reducing file‑descriptor churn and I/O latency. The accompanying key_mappings.json defines millisecond‑accurate start offsets and durations for each logical key identifier, enabling deterministic playback slices.

On the native side, a Rust daemon initializes a Rodio output stream, pre‑loads the entire OGG payload into memory, and registers a global keyboard listener via the rdev crate. Each captured KeyPress event is translated to the canonical identifier used in key_mappings.json (e.g., Space, Enter, KeyA). A lightweight thread spawns a Sink that seeks to the required offset using decoder.skip_duration and plays the slice for the specified duration, achieving sub‑5 ms response times.

For web integration, a minimal TypeScript module creates an AudioContext, fetches and decodes the sprite once, and exposes playKeySound(startMs, durationMs) which slices the AudioBuffer using AudioBufferSourceNode start/stop scheduling. This approach allows any React component to trigger realistic key sounds without additional network requests.

The build topology combines a React UI (styled with Tailwind) compiled to static assets, a Tauri wrapper that embeds the Rust daemon, and standard Node.js tooling (pnpm, .gitignore entries) to keep the repository clean. No external services are required, keeping the attack surface minimal.

Security guardrails include sandboxed audio decoding (Web Audio API runs in the browser context), read‑only access to the bundled assets, and the Rust daemon operating without elevated privileges, ensuring that key capture does not expose sensitive system data.