Starting with cars
Our initial focus is on connecting as many vehicles to DIMO as possible.
Amazon famously sold books before expanding to music, hardware, and cloud services.
By focusing on a specific IoT device category, the core DIMO team will be able to deliver a platform that wins consumer, developer, and enterprise support using our limited resources. Our plan is to generalize the number of devices (and applications) that DIMO supports as we progressively scale and decentralize the protocol.
We selected the connected car category using this simple formula:
πŸ“Ά Coverage X βœ… Quality X πŸ“ˆ Demand = πŸ“Š DIMO Total Value

πŸ“Ά Coverage

How many [devices] can you connect & how much data do they produce? There are 275 million cars in the US alone, and cars produce the most data of any consumer device: 1500x more data per minute than web browsing. Advanced Driver Assistance Systems (ADAS), and vehicle electrification will massively expand the volume of vehicle data as these technologies mature in the next decade.

βœ… Quality

How reliably can you source data & at what intervals? Vehicle data is open & accessible (if you know where to look). Legislation like Right to Repair and car hacker communities like OpenDBC have paved the way for any vehicle owner to plug in a device that records and transmits the information from their car in a usable format while they drive.

πŸ“ˆ Demand

Who cares & how much? What additional analysis do they require? OEMs have committed to aggressive investments in production and R&D to electrify & automate vehicles within 10 years. Batteries and ADAS systems in particular have huge potential liability exposures which can be limited with better data, as information about their real-world performance is inadequately distributed back through the supply chain.

πŸ“ŠDIMO Total Value Connected

The extended market of transactions based on EV data DIMO can collect and validate is large and growing fast. It includes insurance, maintenance, financing, used car sales, fleet operations, charging infrastructure, and more.
Vehicle owners are not currently included in the monetization of this data. Companies like Wejo and Otonomo are purchasing data from automakers (OEMs) unbeknownst to end users, turning cars into Facebook accounts that can’t be deleted. This OEM-controlled structure also reduces the availability, reliability, and neutrality of these data products, creating an unfriendly environment for developers who can generate additional value for connected vehicle owners.
Copy link
Edit on GitHub
Contents