An iPhone app that reads a car through an OBD2 ELM327 adapter and explains its fault codes in plain language, without workshop jargon. It started as a replacement for the app I used with my own car and became a product: started on 11 November 2026, on the App Store since 17 November, free, in 175 countries.
Problem
A sample of App Store reviews of the apps in the category told a clear story. In the most popular one, 6 of 15 negative reviews in the sample said the useful features sit behind the paid version. Across the category, code clearing that stops working after an update, unstable connections and unclear labels came up again and again. Paid versions cost from €8.99 one-off to €44.99, or up to €29.99 a year. None of their App Store subtitles promised to explain things simply. The goal: the same job as the most popular app, made easier to use.
Direction
The name says the idea: a car that talks to you. The brand followed it, "the friendly mechanic who explains things plainly", reassuring without looking like a toy. I compared six brand directions, each previewed on two dashboard cards. I chose to combine the warm workshop palette of one with the type of another: a dark brown background with an amber light and a turquoise accent, for warmth, and Inter Tight with tabular figures for headings and live values, Inter for text. The app is always dark, designed for the car interior in the evening.
UX/UI decisions
Codes explained in plain language, without workshop jargon: what each one means, its most likely causes, and whether it is stored, pending or permanent
Code clearing only with the car stopped and the engine off, after asking "Have you had the fault repaired?". Safety checks repeat every 5 seconds and again right before sending, and the app warns that clearing does not repair the fault
The clear button is always visible: while driving it is disabled and says why. In the first real test on my car the button was missing, because the car was never standing still
A guided connection that shows where the port is and how to turn on the ignition without starting the engine. The app then reconnects by itself and remembers the adapter
Connection states in plain words ("Turn on the ignition", "Adapter not found", "The adapter is not responding"), each with a way out
A dashboard that opens with the car's status in one sentence, then speed and revs in large type, then cards in three sizes that you rearrange like iOS widgets
Make and model read from the VIN, shown with a 3D illustration of the brand's iconic model
Severity shown through light and a coloured card border, never through coloured text, and always with the word that names it, for people who do not tell colours apart. Dynamic Type, bold text, higher contrast, reduced motion and 44-point touch targets
Product decisions
A SwiftUI app plus a separate Swift package for the OBD engine (Bluetooth LE, Wi-Fi, ELM327, protected clearing), testable on its own
A Mac ELM327 emulator and test scenarios (a 2006 diesel, a faulty clone adapter, ignition off), so most of the work happened without a car
A real test on my 2006 Volvo V50 diesel found three problems the emulator had missed: 29-bit CAN, a VIN sent in reverse order by the engine unit and a wrong fuel-type bit. All three were fixed with tests
9,533 generic codes from an open CC0 database. Plain-language explanations for 3,770 of them and 9,126 sentences on likely causes; the other codes show the original English description
Written from scratch, from public protocols and openly licensed data
No account, analytics or ads, and no network calls beyond the local link to the adapter: "Data Not Collected" on the App Store
Free, with no in-app purchases. Cautious App Store metadata: no competitor or car-brand names, no features the app does not have yet
For Apple's review, a demo mode with a simulated car and a fictional VIN, plus step-by-step notes for the reviewer
AI in execution
I decided what to build and the fixed points: written from scratch, safety, privacy, always dark, three tabs. I also set the 11.8-volt battery limit below which clearing is blocked, chose to compete on simplicity and to make it free, approved the screens, submitted the app and released it. I also ran the real tests on my car. Claude wrote the delicate parts of the OBD engine (the ELM327 session, message assembly, connection handling, protected clearing), the experience specification, the brand guidelines, the App Store research and listing and the privacy policy. Codex wrote the Mac emulator and several screens from specifications, and generated the 3D illustrations. Two reviews by another AI model before submission scored the app 5/10 and then 6/10; the issues were fixed after each one.
Outcome
Six days from the start of the project to the App Store (11–17 November 2026). Approved at the first submission, less than 18 hours between sending it and release. 27.4 MB, iOS 18 or later. Released in Italian; an English version is next. No download data yet.






