This roadmap describes intended product direction. It is not a promise that every item will ship in every build.
- Finish Microsoft Store packaging validation.
- Publish GitHub Releases with a portable Windows build and PowerShell installer for users who do not have Visual Studio.
- Add a signed installer or signed package and submit a WinGet manifest once the final app name and package identity are chosen.
- Add a first-run privacy and local-media explanation.
- Improve archive import handling for more ZIP layouts.
- Add stronger export progress reporting for multi-view exports.
- Add better error messages for missing FFmpeg, malformed TeslaCam folders, and corrupt clips.
- Replace prototype metadata labels with a more modern and consistent information layout.
Visual context is planned as a major feature. The goal is to index local clips and create searchable video metadata.
Local visual context will require capable GPU or NPU hardware for practical on-device analysis. Users without suitable hardware should still be able to use the free core viewer, with cloud-based visual context offered later as an optional subscription path.
Planned local visual context features:
- Local frame sampling and scene indexing.
- Local object, motion, and driving-event metadata.
- Ask questions about a clip or a drive, such as "when did a pedestrian appear?" or "show the moment the car changed lanes."
- Flag and separate clips into categories.
- Search by visual events, telemetry events, and time ranges.
- Generate representative frame photos for clips so the clip list can show a visual preview for each drive or segment.
- Explore a gallery-style clip browsing mode for scanning visual context across many clips quickly.
- Keep local analysis available without requiring a subscription on compatible GPU or NPU hardware.
Planned optional subscription features for the free Windows Store version:
- Faster and more accurate visual context through Gemini.
- Cloud-based visual context for devices without suitable local GPU or NPU hardware.
- Cloud-assisted summaries and question answering over selected clips.
- Richer event categorization and metadata extraction.
- Optional Tesla API integrations for vehicle-aware context.
The subscription path must be opt-in and clearly explain what data is sent outside the device. The free core viewer should remain useful without a subscription and should not add ads, promotional overlays, export watermarks, or forced branding. Donations may be offered separately for people who want to support development, signing, hosting, testing, and upkeep.
- More modern and intuitive navigation.
- Cleaner clip list density and sorting controls.
- Customizable design themes.
- Layout customization for camera views and telemetry cards.
- Optional telemetry overlays for clip previews or gallery items, with the default layout keeping telemetry separate so video thumbnails are not covered.
- Better empty states, progress states, and import/export flows.
- Choose the final published app name.
- Develop a final app logo, icon set, and visual identity for the published product.
- Make the logo communicate drive review, camera footage, recording, and telemetry without implying Tesla affiliation or ownership of Tesla marks.
- Replace the current working icon assets with production-ready Windows Store artwork once the final name and logo are chosen.
- Maintain the GitHub Pages site with screenshots, feature overview, download/store links, source-available license summary, privacy policy, free-app positioning, optional support paths, roadmap links, and final branding when the published name is chosen.
Tesla API usage is planned as an optional subscription feature. Possible uses:
- Vehicle metadata enrichment.
- Fleet or vehicle selection.
- Contextual data that improves clip organization.
- Future sync or association between recorded clips and vehicle state.
Tesla API support must be implemented with explicit user consent, secure token storage, and a clear privacy policy update.
The app is planned for eventual Microsoft Store publication under a final product name that differs from this repository's working name. The Store version should be free, with any subscription and donation path clearly separated from the core local viewer. The free version should not add ads, promotional overlays, export watermarks, or forced branding.
A macOS version is also planned. The Windows app remains the first target while the viewer, import, virtual playback, telemetry, and export workflows stabilize.