This is the public-facing map of the current ShoddyTechGarage ecosystem: what each app does, what stage it is in, and where to go next.
Start here if you want to compare the active tracks quickly. If you want build-by-build release detail, the technical trail lives in the Dev Hub.
Each app has a distinct job, maturity level, and next step. The goal is to make the ecosystem easy to scan without flattening everything into one generic “car app” bucket.
A vehicle-focused Android launcher built around readability, live telemetry, large touch targets, and in-car practicality.
A diagnostics and tuning companion focused on connection reliability, safer MicroTune handling, and stronger Bluetooth and wired USB live-data workflows.
An install-aware audio tuning environment built for real vehicles, aftermarket hardware, quick adjustments, deep EQ control, and safer tune experimentation.
A vehicle-aware maintenance environment focused on service history, broad vehicle lookup, build-aware setup, and ownership records that stay useful as the build evolves.
The longer-term direction still reaches beyond the four current app tracks into custom OBD hardware, sensor networks, shared data, and a broader vehicle software stack that can grow with the build.
A tighter set of representative screens keeps the product proof readable while still showing the launcher, telemetry, and setup direction.
Live telemetry, route panel, and media cards tuned for quick in-vehicle visibility.
Role-based launch controls built around daily drivers, tablets, and head units.
Telemetry controls, permissions, and source tuning laid out for different adapter situations.
Vehicle setup checklist that keeps launcher, telemetry, media, and assistant behavior grounded in real device capabilities.
These core screens show how session setup, diagnostics, dashboard layout, and trend tracking actually look in the app without overloading the page.
Overview screen with live session entry points, monitor status, and the most useful scan signals up front.
Summary card that turns live scan results into a readable “what to watch” view instead of dumping raw codes and leaving the user there.
Snap-grid dashboard controls with locked layout handling so the live data view stays readable while driving.
Trend cards for supported PIDs with separate session choices for real capture or demo-driven layout testing.
These current screens show the audio tuning flow from quick daily shaping through Builder Mode detail, setup context, and shell customization.
Dashboard view with workspace mode, preset selection, and Everyday Listening controls visible in one install-aware shell.
Builder Mode brings the deeper DSP-style EQ layout forward, including the horizontal scroll cue for discovering more bands on tablets.
Frequency Guide explains what each band affects so Builder Mode stays readable and safer for intentional tuning changes.
Advanced Setup starts with an optional install profile so Quick Tune can stay simple while deeper defaults remain grounded in the actual vehicle.
System setup covers cabin treatment, head-unit type, subwoofer and amplifier presence, and install notes for more realistic starter behavior.
Settings keep the shared Shoddy shell customizable with theme mode, accent palettes, and a live preview that carries across the AudioLab surfaces.
Current screens show how the app handles garage setup, build-aware vehicle entry, quick mods, and the details needed to keep maintenance tracking tied to the actual vehicle.
Garage home screen with a simple first-use state that pushes straight into adding a real vehicle instead of burying setup.
Build setup flow for factory, modified, engine-swapped, and chassis-swapped vehicles, plus maintenance model selection.
Quick Mods entry with install dates and mileage fields that keep maintenance history connected to real hardware changes.
Vehicle details, VIN, plate, notes, and mileage fields for ownership records that stay useful after the initial setup.
Release history, active development focus, and technical rollout detail live in the developer-facing area instead of being stacked onto the public product pages.
If one of these products already feels like the right fit, use the current testing path to request access. If you still need more detail first, the Dev Hub and update pages stay one click away.