id: ef2e072fff6a4a528b52a6c64daaa267
parent_id: 13c76a5b3d564ce4bfdb4d979d2bfbd0
item_type: 1
item_id: 6c0dcb2a567348fd9796f50c790082e4
item_updated_time: 1782216413393
title_diff: "[]"
body_diff: "[{\"diffs\":[[0,\"0.6\\\n\"],[-1,\"  - [x] Updated README.md with REST API docs, recording docs, updated architecture\\\n\"],[0,\"  - \"]],\"start1\":5808,\"start2\":5808,\"length1\":91,\"length2\":8},{\"diffs\":[[0,\"ation tests\\\n\"],[1,\"\"],[0,\"  - [ ] Add \"]],\"start1\":5834,\"start2\":5834,\"length1\":24,\"length2\":24},{\"diffs\":[[0,\" study |\"],[1,\"\\\n| **RaceChrono** | Real-world mobile lap timer & data logger | n/a (real-world) | See **§18** for full RaceChrono inspiration analysis |\"],[0,\"\\\n\\\n---\\\n\\\n#\"]],\"start1\":17219,\"start2\":17219,\"length1\":16,\"length2\":153},{\"diffs\":[[0,\"--\\\n\\\n\"],[-1,\"*Last updated: 2026-06-08 —\"],[1,\"## 18. RaceChrono — Inspiration & Feature Ideas\\\n\\\n> **Added: 2026-06-23**\\\n> **Source:** https://racechrono.com — RaceChrono Oy (Finland), \\\"The #1 app for motorsports\\\"\\\n> **Context:** RaceChrono is the reference real-world lap timer / data logger app (iOS + Android, 100K+ active users, 4.6/5 Play Store). It targets **cars, motorbikes and go-karts** on closed circuits and point-to-point stages. It is the mobile / real-world analog of what racecraft could become on desktop + sim. Its feature set is a directly relevant source of product and UX ideas, especially for the real-world and karting expansion.\\\n\\\n### 18.1 What RaceChrono Is\\\n\\\n- **Platform:** Native iOS + Android app (RaceChrono Pro = paid with video; RaceChrono = free Android lap timer)\\\n- **Audience:** Track-day drivers, karters, motorcyclists, amateur & some professional racers. Explicitly markets go-karts.\\\n- **Founded 2007** (Nokia S60 origin), EU Regional Development Fund backed for \\\"next generation\\\" data processing.\\\n- **Core promise:** Replaces traditional lap timers and data loggers using a phone + cheap external sensors.\\\n\\\n### 18.2 RaceChrono Feature Set — Idea Source\\\n\\\n| RaceChrono Feature | RaceChrono Tier | racecraft Equivalent Today | Actionable Idea for Us |\\\n|---|---|---|---|\\\n| Lap timing with **sectors + optimal lap** | All | Lap detection pending (§17.3) | Ship lap detection + theoretical best lap (already on roadmap §17.7) |\\\n| **Predictive lap timing + delta-time graph** (live, in-session) | Pro | None — we have post-session only | **HIGH PRIORITY.** Live predictive timing + delta trace is the most-wanted cockpit feature. Ties directly to WebSocket streaming (§16.6 A4). |\\\n| **Track library of >2,000 pre-made tracks** | All | We map per-track manually | **The big one.** Validate our \\\"pre-calculated data library\\\" thesis (Architecture §5). A large, community-contributed track library is the real product/moat. Aim for this scale. |\\\n| **Custom user-defined circuit + point-to-point tracks** | All | TrackMapping use case (done) | Our boundary-recording method is MORE accurate than GPS — market this as a quality differentiator. |\\\n| **Synchronised graph + map + video analysis** | Pro | Graph + map done, no video | Add a synchronized video channel for real-world sessions (and sim replay capture). |\\\n| **Video recording with configurable data overlay** (hardware-accelerated export) | Pro | None | Long-term: render telemetry overlay onto dashcam/footage. Big marketing asset. |\\\n| **Multiple cameras + picture-in-picture export** | Pro | None | Defer — nice-to-have for pro tier. |\\\n| **GoPro® remote control + sync** | Pro | None | If we go real-world, GoPro/AI-1/Aim integration matters. |\\\n| **External GPS receivers** (high-rate, 10–50 Hz) | All | n/a (sim) | Core enabler for real-world / karting. Phone GPS is ~1 Hz, too coarse. |\\\n| **Bluetooth + Wi-Fi OBD-II readers** | All/Pro | None | **Sim-to-real bridge.** OBD-II gives RPM, speed, throttle, temps for real cars. Pairs with §16.6 D6. |\\\n| **Bluetooth LE heart-rate monitors** | Pro | None | Novel **biometric driver coaching** angle: correlate HR spikes with corner commitment / mistakes. Unique differentiator nobody does. |\\\n| **DIY data sources & sensors** | Pro | None | Plugin/extension model for custom data feeds — aligns with our feed architecture. |\\\n| **Unlimited session length (24h races)** | All | Ring buffers (limited) | Ensure storage + manifest scale to endurance sessions. |\\\n| **Data export** (.ODS summary, .NMEA, .VBO, .CSV) | Pro | Raw binary + JSONL | Add analysis-result export (CSV/Excel summary) — trivial, high perceived value. |\\\n| **Cross-platform (iOS + Android)** | All | Web/Tauri desktop | A mobile companion app for post-session review is on roadmap (§16.6 D5). RaceChrono shows mobile is the primary real-world surface. |\\\n\\\n### 18.3 Key Strategic Lessons from RaceChrono\\\n\\\n1. **The data library IS the product.** 2,000+ pre-made tracks is their moat. Our §5 \\\"pre-calculated data library\\\" plan is exactly right — prioritize community track-model contribution + a downloadable library early.\\\n2. **Phone-as-sensor + cheap hardware wins the mass market.** RaceChrono never built hardware; it ingests from commodity OBD-II/GPS/HR devices. We should keep a **hardware-agnostic ingestion layer** and never depend on selling our own sensors.\\\n3. **Video + data overlay is the killer marketing feature.** A driver sharing a lap video with a speed/RPM/track overlay is free viral marketing. Plan for it even if we build it late.\\\n4. **Predictive lap timing drives daily engagement.** It's the one feature racers check every single lap. Build it alongside WebSocket streaming.\\\n5. **Real-world + sim from one analysis engine** = our long-term edge. RaceChrono is real-world only and has no sim pipeline; Track Titan is sim only with no real-world. Owning both is wide-open.\\\n6. **Biometrics are an unexplored frontier.** HR-monitor integration for \\\"you braked early every time your heart rate spiked in the braking zone\\\" coaching is genuinely novel.\\\n\\\n### 18.4 Concrete RaceChrono-Inspired Additions to Our Roadmap\\\n\\\n| Idea | Maps To | Priority |\\\n|---|---|---|\\\n| Live predictive lap timing + delta graph | §16.6 A4/A5/A6 (WS + lap detection + reference lap) | P0 |\\\n| Community track-model library (target 100s → 1,000s of tracks) | Architecture §5, §16.6 D1/D2 | P1 |\\\n| Hardware-agnostic ingestion: GPS / OBD-II / external sensor feeds | §16.6 D6, new TelemetryFrame sources | P1 |\\\n| Synchronized video channel + data overlay export | New feature line | P2 |\\\n| CSV / Excel session-summary export | New endpoint | P2 |\\\n| Biometric driver coaching (HR monitor) | New feature line | P3 |\\\n| Mobile companion app (post-session review) | §16.6 D5 | P3 |\\\n\\\n---\\\n\\\n## 19. Karting Market & Styria Karting Partnership\\\n\\\n> **Added: 2026-06-23**\\\n> **Context:** Karting is a natural and currently underserved adjacent market. It bridges sim and real-world racing, has a passionate enthusiast + amateur-competition audience, and offers a concrete go-to-market path via a local partner.\\\n\\\n### 19.1 Why Karting Fits racecraft\\\n\\\n- **Real-world telemetry gap:** Karts have almost no built-in data acquisition. Enthusiasts and rental/amateur racers rely on phone GPS (1 Hz, inaccurate) or expensive Aim/Unipro displays. This is exactly RaceChrono's sweet spot (§18) — and RaceChrono's mass-market weakness (GPS accuracy) is our potential edge.\\\n- **Bridge between sim and real:** Sim racing-to-karting is a recognized pipeline (many karting schools and sim centers pair them). racecraft could offer **one coaching engine across sim practice and real kart laps**.\\\n- **Lower barrier to hardware:** Karting data sources are simple — wheel speed pickup, engine RPM, optional GPS, optional OBD-II on some 4-stroke karts. Minimal custom hardware needed.\\\n- **Coaching needs are concrete and high-value:** braking consistency, racing line, sector deltas, theoretical best lap, consistency across stints. All are already on our roadmap (§17).\\\n- **Strong community + content loop:** Karters love comparing laps and sharing data (social/leaderboard dynamics) — feeds the data-network flywheel (§5).\\\n\\\n### 19.2 Karting-Specific Features to Consider\\\n\\\n| Feature | Why It Matters for Karting | Our Status |\\\n|---|---|---|\\\n| Theoretical best lap + sector deltas | The #1 thing karters want to improve | §17.7 — planned |\\\n| Racing-line / line-deviation coaching | Margins are tiny in karting; line is everything | §17 corner analysis — planned |\\\n| Consistency scoring across stints | Detect fatigue / setup changes over a session | New metric |\\\n| Grip/surface awareness (outdoor tracks, changing grip) | Outdoor karting grip varies hugely by weather | Real-world surface data needed |\\\n| Lightweight mobile capture (phone + external GPS) | Karters won't bring a laptop trackside | §16.6 D5 mobile companion |\\\n| Lap-by-lap shareable video+overlay | Viral social content at the track | §18 video overlay idea |\\\n| Rental-kart leaderboard by venue | Engages casual/rental drivers, drives acquisition | New community feature |\\\n\\\n### 19.3 Go-To-Market: Partner with a Karting Venue\\\n\\\nA single anchor venue gives us real data, a test bed, credibility, and a first distribution channel. **Styria Karting** (Steiermark / Styria region, Austria) is identified as a strong candidate partner. (Note: exact venue identity, scale, and contact details need to be verified — capture the lead and research the specific operator.)\\\n\\\n### 19.4 Proposed Styria Karting Partnership — Concept\\\n\\\n| Aspect | Proposal |\\\n|---|---|\\\n| **Partner** | Styria Karting (regional karting venue/operator in Styria, Austria) |\\\n| **What they provide** | Real karting track(s) for data capture + track modelling; access to drivers/sessions; venue as distribution channel |\\\n| **What we provide** | Free pilot of racecraft analysis for their drivers; venue-branded leaderboards; coaching reports; track models of their circuits |\\\n| **Pilot scope** | 1 track, ~10–20 drivers over 2–4 sessions; capture real telemetry (GPS + engine RPM), build TrackModels, validate coaching output vs. perceived value |\\\n| **Validation goals** | (1) Can we capture usable karting data? (2) Do drivers find the coaching actionable? (3) Does a venue-branded leaderboard drive engagement/acquisition? |\\\n| **Commercial model (if pilot succeeds)** | Revenue share or per-venue license; white-label \\\"powered by racecraft\\\" for the venue; freemium for individual drivers with upsell |\\\n| **Why Styria** | Local/regional → low-friction relationship; potential for in-person testing; Austrian motorsport ecosystem (Red Bull Ring proximity, karting tradition) |\\\n\\\n### 19.5 Immediate Next Steps — Karting Track\\\n\\\n1. **Verify the partner:** Identify the exact Styria Karting venue/operator, scale, facilities, and a contact. (Lead captured from this session; research needed.)\\\n2. **Define karting data capture:** Decide minimum viable data source for karts (external 10 Hz GPS + engine RPM pickup). Determine whether phone-based capture (RaceChrono-style) or a small logger is needed.\\\n3. **Draft a one-page pilot proposal** for the venue (free pilot → data + leaderboards → revenue share).\\\n4. **Re-tag** relevant notes (karting, partnership) once the partner is confirmed.\\\n5. **Add karting** as a tracked segment in the product roadmap (§16.6) — likely a Phase B/C initiative alongside rally.\\\n\\\n---\\\n\\\n*Last updated: 2026-06-23 — Added §18 (RaceChrono inspiration & feature ideas) and §19 (Karting market + Styria Karting partnership).\"],[0,\" rac\"]],\"start1\":30716,\"start2\":30716,\"length1\":35,\"length2\":10476},{\"diffs\":[[0,\"ion, purchase DiRT Rally 2.0\"],[1,\", research Styria Karting partner.\"],[0,\"*\"]],\"start1\":41534,\"start2\":41534,\"length1\":29,\"length2\":63}]"
metadata_diff: {"new":{},"deleted":[]}
encryption_cipher_text: 
encryption_applied: 0
updated_time: 2026-06-23T12:07:21.159Z
created_time: 2026-06-23T12:07:21.159Z
type_: 13