Build on DIMO - April 2024

Overview

Last month, Build on DIMO teased Developer Licenses and applications built on DIMO. In this edition, the shiny end-to-end Developer License process, which interacts with the blockchain, is showcased, along with an interview with DIMO in-house builder, Laura.

Developer Licensing

Building on DIMO has never been easier. The DIMO Developer License is a gateway to accessing a range of APIs and tools that enable seamless integration with the DIMO Network. A Developer License lets you embark on a journey to retrieve data from tens of thousands of vehicles connected through DIMO hardware and software integrations.

Through a 4-step process interacting on Polygonscan, builders can now provision their own API access without the back-and-forth with a DIMO core dev. This self-service model on the blockchain is the DIMO Network’s first stride to building something grander. Here’s an overview of what the process looks like:

Still confused? Well, the abstraction and underlying decentralization mechanism should at least let you feel safe and secure as a builder. The DIMO community is committed to building a better developer experience. The Developer Console to orchestrate all the processes is currently in development. Check out below for a sneak preview.

Sign up with your provider of choice, the Build on DIMO Developer Console will be your one-stop-shop for developer needs.

Simply create an app and generate API credentials for your developers, simplifying the Developer License process.

Manage your apps for all environments in one consolidated view: sandbox or production.

Builder Interview

In this engaging conversation with a software engineer who embarked on her DIMO journey in 2023, delve into the intricacies of building with the DIMO API. Here's a glimpse into her experience, hurdles encountered, and the lessons learned along the way.

Can you tell us a bit about yourself?

Sure, I'm a software engineer who joined DIMO fresh out of college in 2023. My work primarily revolves around building and testing APIs. Having some experience in the automotive field, DIMO presented itself as an intriguing opportunity post-graduation.

What app did you build using the DIMO API?

I developed the DIMO Trips Beta app, an authenticated version of our internal Trips app. It allows users to log into their web3 wallet and displays a list of trips they've taken.

On a scale from 1 to 5, how straightforward was the DIMO API integration process?

I'd say a 4. My perspective might be slightly biased since I've been involved in building some of the SwaggerDocs and the APIs themselves.

Were there any resources or tools that particularly helped you? Or something that could have made the process easier?

The SwaggerDoc pages were invaluable as they provide a clear baseline of what the requests and responses should look like.

Did you face any significant challenges during the development? How did you tackle them?

Yes, authentication on the frontend was a bit of a hurdle. Out of all the options, I ended up choosing Rainbowkit 🌈 to integrate with, but it took me about a month to sort everything out. 

How did the data quality and availability from the DIMO API impact your app?

The data quality and consistency are generally good. However, we did face some challenges, especially with device data and ensuring location-related data was accurate and timely. We had to do some heavy lifting on the client side to ensure data reliability.

Comparing your experience with DIMO to other APIs, how does it stack up?

The API documentation is quite comprehensive, especially for developers who may not have extensive experience. The clear documentation on authentication and examples provided are particularly helpful for newcomers.

How would you rate the support and documentation provided by DIMO?

Again, a 4 out of 5. The documentation is well-hyperlinked, and there's plenty of it to guide you through. It's basically documentation on documentation, which is great for learning.

Were there aspects of the DIMO API that you found more challenging or limiting compared to others?

Yes, the behavior of API endpoints isn't uniform across the stack. Some are token-based, some public, and others require privilege tokens. Recognizing and adapting to these differences was a bit of a learning curve.

What’s one piece of advice you would offer to other developers?

Read the doc 😀 - sounds simple, but it's crucial. The documentation is there to help and guide you through the process.

--

Hope you find this Q&A session insightful. It sheds light on the practical aspects of working with the DIMO API but also underscores the importance of documentation, adaptability, and the right tools in overcoming development challenges that you may also face.

Join the Community

Join a community that’s eager to innovate. The DIMO ecosystem offers a supportive space for developers to share ideas, team up on projects, and explore the future of digital mobility. Plus, the DIMO Foundation's Ignite Grants program is here to support your projects financially, so pitch away. Engage the DIMO community and core devs in a conversation and learn more in the #built-on-dimo channel on our Discord server 🥳