Long-term vision โ€ข modular ecosystem

Long-Term Goals

ShoddyTechGarage LLC is not just about building apps or working on one vehicle. The long-term vision is a complete ecosystem where vehicles, software, and hardware all work together seamlessly.

The target is a modular platform made of interconnected systems that evolve with the vehicle, the driver, and the build itself instead of locking everything into one fixed setup.

Core ecosystem

The future ShoddyTechGarage LLC platform is meant to be more than a launcher or a scanner. It is a family of systems that share context, share data, and work together as one coherent automotive platform, with ShoddyDrive as the primary lane and ShoddyScan plus ShoddyHub as second-tier hero lanes.

Hero roadmap lanes

Roadmap priority follows the same product hierarchy: ShoddyDrive is primary, while ShoddyScan and ShoddyHub (Hardware) are second-tier hero lanes. ShoddyTune is now the alpha Android companion surface for the tuning work that moved out of ShoddyScan.

Primary lane

๐Ÿš—ShoddyDrive

The daily-driver shell for route context, telemetry visibility, media flow, assistant access, and in-vehicle readiness checks.

  • Driver-first launcher flow tuned for real head units and tablets.
  • Live telemetry and diagnostics awareness that stay readable while driving.
  • Assistant-ready context with practical disclosure and fallback behavior.
  • App Bridge resilience work focused on steadier in-car signal confidence.

This is the operational front-end of the ecosystem.

Secondary hero

๐ŸงชShoddyScan

The diagnostics workspace for evidence-first troubleshooting, transport clarity, assistant-supported interpretation, and support-ready reports.

  • Consolidates diagnostics, assistant context, telemetry, and health-trend workflows.
  • Improves scan, home, tune-review, and report surfaces with cleaner summary wording.
  • Moves tuning work out of ShoddyScan and into ShoddyTune so diagnostics stay clear and evidence-first.
  • Improves reliability by surfacing failed scans and degraded sessions honestly instead of hiding failure states.

This is the diagnostics backbone of the ecosystem.

Secondary hero

๐ŸงฉShoddyHub (Hardware)

The hardware lane of the roadmap, focused on modular add-ons and integration points that connect software workflows to real vehicle signals.

  • Active research lane with clear validation boundaries while compatibility expands.
  • Targets sensor hubs, bridge modules, and service-friendly interface design.
  • Built to cooperate with ShoddyDrive and ShoddyScan context first, then broader ecosystem lanes.
  • Prioritizes practical install constraints, safer fallback behavior, and honest diagnostics.

This becomes the hardware expansion lane behind the broader ShoddyHub direction.

Hardware companion lane

ShoddyTune sits beside ShoddyHub Hardware as the tuning-facing app layer, not as a broad unsupported write tool.

First alpha

๐ŸŽšShoddyTune

The Android companion surface for ShoddyHubHardware, replacing the former MicroTune lane from ShoddyScan with a cleaner place for tuning review, sample-data ingest, and guarded handoff.

  • Keeps ShoddyScan focused on diagnostics, support evidence, and report clarity.
  • Evaluates and ingests sample data through the ShoddyHubHardware API.
  • Builds tuning workflows around explicit safety gates and verified controller behavior.
  • Does not include flash or write tooling in the first alpha build.
  • Connects user-facing review screens to the host and interface hardware boundaries described in ShoddyHub.
  • Starts LL8-first and expands only where validation supports it.

This becomes the tuning-facing app layer for the hardware ecosystem.

Supporting ecosystem lanes

These tracks remain important to the long-term platform, but they are supporting lanes rather than hero priorities.

Supporting lane

๐Ÿ”งShoddyMaintenance

A smart, vehicle-aware maintenance system built to go beyond simple reminders and fixed schedules. The initial release is now documented in the Dev Hub so the maintenance lane has a real public baseline.

  • Tracks real service intervals using live vehicle data.
  • Integrates with OBD2 and custom sensor inputs.
  • Predicts wear based on driving behavior, not just mileage.
  • Maintains a full digital service record for builds and daily drivers.

This becomes the health system of the vehicle.

Supporting lane

๐Ÿ”ŠShoddyAudioLab

A dedicated audio tuning and control environment built for real-world installs instead of generic one-size-fits-all presets. The first closed-testing build is now documented in the Dev Hub.

  • Install-aware vehicle setup for more relevant tuning baselines.
  • Quick Tune controls for rapid day-to-day adjustments.
  • Builder Mode EQ tuning for hands-on system dialing.
  • Live adaptive sound adjustment tied to real-world driving context.
  • Garage storage for custom tunes and rollback snapshots.

This turns the vehicle into a fully tunable sound environment that can grow from quick tweaks to full custom builds.

Supporting lane

๐Ÿ› ShoddyBuild

A build-planning and execution workspace that keeps project-car progress organized from first plan to final verification.

  • Tracks timeline milestones, parts, tasks, and spend in one lane.
  • Keeps build history clear so decisions and revisions stay traceable.
  • Supports practical planning across daily-driver and project-car workflows.
  • Prepares cleaner handoff context for diagnostics, maintenance, and future hardware work.

This becomes the planning and execution memory of the ecosystem.

Supporting lane

๐Ÿค–ShoddyAssistant

An in-vehicle AI assistant focused on function, clarity, and real utility rather than novelty.

  • Offline-first design with optional cloud expansion.
  • Assists with diagnostics, vehicle status, and system control.
  • Translates vehicle data and issues into plain language.
  • Acts as a true co-pilot instead of just a voice command layer.

This becomes the intelligence layer of the ecosystem.

Supporting lane

๐Ÿ“ฑShoddyAndroidOS

A custom Android-based vehicle operating system and ROM designed specifically for automotive use.

  • Starts from Android 13 with room to move forward to newer versions.
  • Built for head units, tablets, and embedded in-vehicle systems.
  • Supports DIY hardware such as ESP32 sensor hubs, OBD2 integrations, and standalone modules.
  • Optimized for performance, readability, and driver-safe interaction.
  • Natively integrates with ShoddyDrive, ShoddyScan, ShoddyAudioLab, ShoddyBuild, ShoddyMaintenance, ShoddyHub (Hardware), and future modules.
  • Scales from budget setups to high-end custom builds.

This is the foundation layer: a true car OS built for users and builders.

The end goal

The long-term target is a unified system where vehicle, data, control, and intelligence all come together into one seamless, evolving experience.

Whether the platform is used in a daily driver, a project car, or a full engine-swap build, every layer should work together, speak the same language, and grow with the build.

What that means in practice

  • Shared context Apps, hardware modules, and sensors all understand the same vehicle state.
  • Shared control Maintenance, diagnostics, audio, build planning, and hardware systems can cooperate instead of living in separate silos.
  • Shared growth The platform can start simple and expand as the vehicle and the builder demand more.
  • Shared language Data stays understandable and useful instead of being trapped behind black boxes.

Built to evolve

The point is not one perfect app or one finished build. The point is an ecosystem that can keep evolving alongside the vehicle, the driver, and the tools around it.