Every repair in fixin for iPhone and iPad follows the same path: you show the app the problem, it tells you what it thinks is wrong, it writes the procedure for that specific fault, and it works through the job with you. The whole diagnosis runs on your device — no upload, no signal required.
Open Quick Diagnose and photograph the problem — a warning light, a leak, a cracked fitting, a stain on a ceiling. Framing guides help you get a shot the model can actually read on the first try.
The image is classified on your device by the Ruby 3.9 engine. Nothing is uploaded to identify it, so the analysis works the same in a parking garage or a boatyard with no signal as it does on wifi.
Classification comes back with the domain and the final diagnosis named outright — Boat, impeller failure — rather than a list of things it might be. From there the screen becomes the hub for the job: repair instructions, the parts and tools it calls for, and support options if you want a professional.
What sits below that adapts to the domain. A marine diagnosis surfaces engine hours, drive type, and sea conditions; a car surfaces OBD-II codes and service history. Assign the diagnosis to a project and it files itself with the other work on that boat, vehicle, or house.
From the diagnosis, fixin writes the procedure for that fault — not a generic article for the category. Immediate safety actions come first, then the ordered steps, then the parts and tools the job actually calls for.
Part numbers, torque figures, and service intervals are pulled in where they apply, so you are not cross-referencing a forum thread halfway through the job.
The instructions become a worksheet you actually work from. Tick each step off as you go and the progress ring tracks the job; reorder steps that make more sense in a different order, edit the wording for your own setup, or add a step the guide didn't know about.
The AI Coach stays available while you work, and the finished worksheet stays attached to the project — so next season there is a record of what was done. If the job turns out bigger than it looked, hirin hands it to a professional with the diagnosis already attached.
fixin for Android follows the same four steps as iOS — the engine, the diagnosis, and the repair worksheet are the same. The screenshots below are being captured on Android now; the walkthrough is accurate today, the images are the placeholder.
Open Quick Diagnose and photograph the problem — a warning light, a leak, a cracked fitting, a stain on a ceiling. Framing guides are still being tuned per device, so on some Android hardware you may need a second shot.
The image is classified on your device by the Ruby 3.9 engine, exactly as it is on iOS. Nothing is uploaded to identify it, and a diagnosis works with no connection at all.
Classification comes back with the domain and the final diagnosis named outright, and the screen becomes the hub for the job: repair instructions, the parts and tools it calls for, and support options if you want a professional.
What sits below that adapts to the domain — engine hours and sea conditions for a boat, OBD-II codes and service history for a car. Assign the diagnosis to a project and it files itself with the other work on that boat, vehicle, or house.
From the diagnosis, fixin writes the procedure for that fault — not a generic article for the category. Immediate safety actions come first, then the ordered steps, then the parts and tools the job actually calls for.
Part numbers, torque figures, and service intervals are pulled in where they apply, so you are not cross-referencing a forum thread halfway through the job.
The instructions become a worksheet you work from. Tick each step off as you go and the progress ring tracks the job; reorder steps, edit the wording for your own setup, or add a step the guide didn't know about.
The AI Coach stays available while you work, and the finished worksheet stays attached to the project. If the job turns out bigger than it looked, hirin hands it to a professional with the diagnosis already attached.