As promised, last week we published a roadmap for the DIMO Developer Platform that covers the work expected between now and the end of 2024. There’s a lot there, but my three favorite things on the roadmap are:
The DIMO Developer Console, which will make it extremely easy for developers to sign up and get started;
The Wallet as a Service (WaaS) which will be a cutting edge implementation of account abstraction, allowing users to create an account on DIMO (within DIMO Mobile or other apps) and easily share data across the DIMO ecosystem;
Vehicle decoding progress: we’re finally starting to deploy more vehicle codes that provide users more data about their vehicles and enrich the value of the DIMO Developer Platform.
All of these are major developments. Within the next few weeks we’ll have the Developer Console live making it easy for developers to create their Developer license and start building. As they consume data, these developers will need DIMO Credits, creating protocol burn, as hypothesized in this draft proposal. Protocol revenue is good.
The DIMO Wallet as a Service is also unique and important. We’re using building blocks Turnkey and Zerodev to create an embedded wallet that will service the entire DIMO Ecosystem. Let’s say you’re signing up for DIMO Mobile: you’ll be able to create an account with an email address and you’ll still be able to do any onchain actions required, but the web3 will be in the background. If another app — let’s say a used car marketplace — wants to allow DIMO users to connect and share car data, they can embed a “Login with DIMO” button that makes use of the same wallet, providing a seamless experience for users. It’s web3 without the wires, a consumer experience that anyone can grasp.
These pieces above become even more useful when there is more vehicle data. In the last months, we’ve had a few community decoders come forward. One decoder has provided more than a dozen pull requests with new data for a range of vehicles on DIMO. We’re working with another decoder with massive quantities of vehicle codes to get their codes in queue for testing and deployment. Last but not least, we’re finalizing the deployment of UDS queries, another type of vehicle data protocol. Within the week we’ll publish a public spreadsheet of the data queue so that any user can find out what data they are able to collect for their vehicle.
The foundation is improving constantly. Soon enough, the magic will be live and in users’s hands.
