I've recently done some work for a startup that is developing a highly comparable product.<p>I strongly doubt their "works on any car since 1995" claim. While OBD-II has been an official standard for very long, not all cars support it equally well at all. We've had serious trouble getting it to work with A-brand cars made in e.g. 1999.<p>Therefore, I believe that them making this claim can mean one of two things:<p><pre><code> - They're lying
- Their "prototype" has seen little field testing at this point.
</code></pre>
That said, honesty be told, we've been testing in Europe, where the OBD standard has been adopted later. My impression is that moj.io is a North-American only product. Maybe this makes all the difference.<p>Additionally, however, "Virtual Mechanic" based on OBD-II alone is going to be a half-assed feature (to my understanding). OBD-II contains little more error reporting than that related to emission (i.e. your engine). If your airbag or your breaks malfunction, then this may only be reported through manufacturer-specific protocols. Most importantly, this would mean that a light in your dashboard may be lit, while the Moj.io app says "Running Great!" I highly doubt that they have implemented all manufacturer-specific protocols to a sufficient extent for this feature to work well. It is technically possible, but it needs either a lot of reverse engineering, or a lot of purchased IP.<p>I really like the other features (FamilyConnect, etc), though, and how they're presented. Well done!<p>Still, while I like this approach, and while I want this badly myself (and a lot of moj.io seems better planned, marketed and designed than what I've been involved in), based on the above I have strong doubts.<p>Now, I understand that this may be hard criticism, and maybe I'm completely wrong about some aspects - I'm no real expert here. So if one of the founders reads this, feel free to correct me!