How flappedear/telemetry works
FlappedEar Telemetry is a cross-platform track-day analysis app. The main workflow is to import RaceChrono recordings, calculate laps and day results, then explore maps, charts, comparisons and derived reports. The README documents these product capabilities, but the supplied source excerpts do not include the Flutter UI or most runtime implementation. Accordingly, links between product stages below reflect documented behavior; the available core package path is the only source location shown for its recording and analysis model.
Main entry points: telemetry_core Telemetry core
Components 17
Recording import
- Import a day
- VBO / RCZ recordings
Lap analysis
- Telemetry core
packages/telemetry_core - Lap timing
packages/telemetry_core - Approved segments
packages/telemetry_core
Results exploration
- Day results
- Lap map and charts
- Lap comparison
- Corner Analyzer
- Theoretical best
- Time losses
- Consistency and progression
- Driving insights
- Day report
Day data
- Saved day
- Day storage
Other components
- Driver
Connections 16
- Driver → Import a day: chooses recordings
README.md - VBO / RCZ recordings → Import a day: supplies files
README.md - Import a day → Telemetry core: prepares recordings
README.md - Telemetry core → Lap timing: calculates laps
- Telemetry core → Approved segments: proposes segments
README.md - Import a day → Day results: shows results
README.md - Day results → Lap map and charts: opens lap
README.md - Day results → Lap comparison: compares laps
README.md - Lap comparison → Corner Analyzer: analyzes corners
README.md - Day results → Theoretical best: shows segment losses
README.md - Day results → Time losses: ranks losses
README.md - Day results → Consistency and progression: summarizes trends
README.md - Lap comparison → Driving insights: shows driving metrics
README.md - Day results → Day report: presents report
README.md - Driver → Saved day: saves or opens
README.md - Saved day → Day storage: reads and writes
README.md