Re: Introducing DIMO Build

It’s interesting to be writing this again 8 months after our initial launch of the DIMO Developer Console on August 8, 2024 (8/8/2024). The series of 8’s creates this serendipitous alignment, especially when 8 symbolizes wealth and prosperity in many cultures. With the new DIMO Build, we're not just refreshing our branding and themes; we're opening the door to a new era of decentralized possibilities. This enhanced Console lays the foundation to the DIMO Protocol and all of you to build with greater freedom and flexibility.

Re: Branded

🎨 DIMO Themed

The Console theme has been updated to align with DIMO's new visual identity, incorporating new colorways and font styles for a more uniform user experience.

🎯 User-Centric & Future-Proof Experience

Every flow within the Console has been reviewed and aligned with future expansion projects, including webhooks, low-code tools, developer billing, DIMO Oracles, you name it - the console user experience is designed with future-proof concepts in mind.

> Less distractions, more focus

Re: Engineered

🤝 Social Logins

Social logins are one of the most under-the-radar updates in this new version. Behind the scenes, we consolidated the social logins to integrate directly with the DIMO Auth Servers. This helps streamline the protocol’s operations while eliminating the one-off configurations on the Console. Also, we added Apple logins to align with the DIMO Mobile app users in case you used your Apple credentials to login.

🤳 OTP Login Mechanism & Sessions

Having every user logging in using passkeys is the end vision, however, we also realized that many of you might have device or browser compatibility issues when using passkeys. One of the core re-engineered pieces was how the login flow now offers the ability for end users to dismiss passkey prompts and defer back to using email OTP login. Also, each login now creates auth sessions.

> Less signing (of transactions), more building

😵‍💫 Reduced Jargons & Abstractions

The original Console had some abstract concepts that we added in to help bridge the gap between web2 and web3. Since the initial release, we’ve interacted and learned from many developers in the ecosystem regardless of their background, and removed lots of the complicated jargon and abstractions. This includes the consolidation of “apps” which you’ve all heard about in the previous newsletter posts, and prepping for our next major project - Developer Billing.

⛓️ Embraced Decentralization

The original Console had many components that just weren’t ready for decentralization at the time, namely how developer licenses were handled and displayed. With our movements to fully-decentralize, developer license information was added to the Identity API and on the Console, it now maps directly to on-chain data.

This removed the dependency on an off-chain database where discrepancies may occur, while providing the world with an open registry of DIMO App Developers. The amount of tech debt we prevented was immeasurable because of this quick pivot. You can now check any developer licenses via the Console, and explore the sea of applications which leads to our upcoming projects (to be announced).

> Less centralization, more transparency

🆕 Vehicle List

The new Console also utilizes more of the Identity API to provide insights to any license. Under License Details, you’ll now find a list of vehicles with corresponding on-chain vehicle ID, make, model, and year. This gives you a quick overview of what has been shared with your license.

🧰 Developer Support

This finishing touch entails setting up our first developer support pipeline. With a dedicated line to reach our Developer Relations team, you will not be running around trying to get in touch with the right person at DIMO. The contact form directly puts you through to our engineers that built the Console and the whole experience, cutting out the middlemen.

> Less kicking around, more kick to score ⚽