i99dash for developers
Build mini-apps that run on i99dash car head-units. From zero to published in five minutes.
i99dash hosts third-party mini-apps on a car head-unit. A mini-app is a
plain HTML / JS / CSS bundle the host loads inside a sandboxed web view. It
reads context (active user, current car, locale, theme) and proxies API calls
through a typed JS bridge — getContext() and callApi().
Should I build a mini-app?
Yes if you want to:
- Show information to drivers (fuel prices, weather, EV charging stations, parking lots) — these are read-only mini-apps, public catalog.
- Build a privileged tool (diagnostics, log tailing, package management) for
fleet operators or your own team — these are
@i99dash/admin-sdkmini-apps, restricted distribution.
No if you want to:
- Control the car (lock doors, set AC, drive). The SDK is read-only by
construction. There is no
client.car.lockDoors(). - Build a native head-unit app. Mini-apps are HTML/JS — for native, talk to the host team directly.
Start here
1 → Quickstart (5 min)
Scaffold, edit the simplest real code, publish a hello-world.
2 → Concepts
The bridge, calling your backend, error model. The mental model the rest of the docs assume.
3 → Build something real
Fetch JSON from your backend, render a list, handle errors. ~10 minutes.
Reference, when you need it
Guides
Best practices, subscriptions, testing — read before shipping.
Recipes
Copy-paste end-to-end builds.
API reference
Auto-generated TypeScript reference for every public symbol.
Troubleshooting
Symptoms, root causes, fixes.
Glossary
One canonical definition for every term across the docs. Search this if a word feels overloaded.
What's new
- Beta testing track — publish to a limited cohort first (TestFlight-style). Read the guide.
Working with AI agents
The site exposes /llms-full.txt (every page as plain
markdown) and an MCP server at /api/mcp
with tools search_docs, get_doc, list_packages, list_symbols. Add it
to Claude Code:
claude mcp add --transport http i99dash-docs https://docs.i99dash.app/api/mcp