LiveSplit One is a cross-platform speedrun timer application, the successor to the classic LiveSplit timer. It runs as a Progressive Web App and as a Tauri desktop application, targeting Windows, Linux, and macOS. The core timing logic is compiled to WebAssembly via the 'livesplit-core' Rust library, while the UI is built with React 19, TypeScript, and Vite. The application provides a rich set of features for speedrunners: highly customizable split timers, real-time comparisons, layout editor with drag-and-drop, integrated leaderboards from Speedrun.com, global hotkeys (desktop only), always-on-top mode, WebSocket server for remote control, and support for multiple timekeeping methods (real time vs game time). Data persistence is handled via IndexedDB in the browser and the filesystem in Tauri. The codebase is well-structured with a clear separation between core logic (WASM), UI components, and platform-specific code, though some central components like 'LiveSplit.tsx' are large and could benefit from further decomposition.
This repository is a comprehensive curated knowledge base and reference directory focused on time tracking, productivity methodologies, and related tools. The dominant character is a flat collection of over 3000 markdown files under `details/`, each describing a specific software tool, productivity technique, author, or research finding in a structured format (overview, features, pricing, use cases). While primarily a reference resource, the repo also contains a few functional software components, including a Spring Boot + Vaadin reporting app for Toggl (toggl-reporter), a Django monorepo with REST API and Keycloak auth for time tracking (timed), a Home Assistant custom component (ha-toggl-track), and a Lua SDK (Qmonix). These are small reference implementations that demonstrate integration patterns. The repository serves as a one-stop guide for individuals and teams evaluating time tracking solutions, learning productivity methods, or building integrations. It cites numerous statistics and studies, but many entries are stale or incomplete (e.g., research stub pages with placeholder text). The code components are basic and not production-ready without further development.