Bogdan Mavrin
Mozverse Console
Mozverse Console
Role
Product Designer
Platform
Web + Mobile
Scope
UX/UI Design, Branding
About Mozverse
Mozverse is a Web3 company building developer tools and infrastructure for blockchain and metaverse projects. The team offers several core technologies, such as Ultranode, NFT API and Web3 Data/IPFS Storage, all designed to make building decentralized applications faster and more scalable.
The company set out to create a single console that would unify these tools under one roof. Developers used to switch between APIs, dashboards, and docs — now they needed one workspace where they could manage requests, logs, and analytics seamlessly. Essentially, the goal was to turn Mozverse into a complete ecosystem for Web3 builders.
Mozverse is a Web3 company building developer tools and infrastructure for blockchain and metaverse projects. The team offers several core technologies, such as Ultranode, NFT API and Web3 Data/IPFS Storage, all designed to make building decentralized applications faster and more scalable.
The company set out to create a single console that would unify these tools under one roof. Developers used to switch between APIs, dashboards, and docs — now they needed one workspace where they could manage requests, logs, and analytics seamlessly. Essentially, the goal was to turn Mozverse into a complete ecosystem for Web3 builders.
Main Task
The early alpha already brought key technologies together, but it still felt rough, with disconnected layouts, fragmented flow, and no shared design system. It worked, but not well enough for daily use.
Our goal with the MVP was to turn it into a unified, reliable platform by refining its hierarchy, aligning the visual language, and ensuring a consistent experience across modules.
As the Design Team, we shaped the console end to end: we defined goals, mapped flows, and built a scalable UI system that connected every piece.
Ultimately, our focus was on creating a workspace that felt dependable and effortless to use, where every tool supported the same logic.
The early alpha already brought key technologies together, but it still felt rough, with disconnected layouts, fragmented flow, and no shared design system. It worked, but not well enough for daily use.
Our goal with the MVP was to turn it into a unified, reliable platform by refining its hierarchy, aligning the visual language, and ensuring a consistent experience across modules.
As the Design Team, we shaped the console end to end: we defined goals, mapped flows, and built a scalable UI system that connected every piece.
Ultimately, our focus was on creating a workspace that felt dependable and effortless to use, where every tool supported the same logic.
01. Discovery Phase
Our timeline was tight — about two months for a full redesign and UX unification across all tools. We worked as a small distributed team: two product designers, a front-end lead, and two engineers covering both API and infrastructure.
We started with interviews of developers already using the early APIs. Their feedback clarified what “fast” and “usable” meant in day-to-day work. Many of them shared that the console felt fragmented and hard to navigate. The flow didn’t reflect how they actually worked, since moving between requests, logs, and analytics required too many steps and felt disconnected. These insights became the foundation for reorganizing the console around real developer behavior.
From there, we outlined a few key focus areas to make the console more consistent and developer-friendly:
Shorten the path from first login to first successful request.
Unify logic across modules (Ultranode, NFT API, Request Builder).
Improve visibility of logs and analytics.
Make the Console scalable, ensuring that new modules fit naturally into the same structure.
Our timeline was tight — about two months for a full redesign and UX unification across all tools. We worked as a small distributed team: two product designers, a front-end lead, and two engineers covering both API and infrastructure.
We started with interviews of developers already using the early APIs. Their feedback clarified what “fast” and “usable” meant in day-to-day work. Many of them shared that the console felt fragmented and hard to navigate. The flow didn’t reflect how they actually worked, since moving between requests, logs, and analytics required too many steps and felt disconnected. These insights became the foundation for reorganizing the console around real developer behavior.
From there, we outlined a few key focus areas to make the console more consistent and developer-friendly:
Shorten the path from first login to first successful request.
Unify logic across modules (Ultranode, NFT API, Request Builder).
Improve visibility of logs and analytics.
Make the Console scalable, ensuring that new modules fit naturally into the same structure.
Next, we defined the MVP structure of the platform, focusing on a clean, developer-first flow built around real usage patterns.
Next, we defined the MVP structure of the platform, focusing on a clean, developer-first flow built around real usage patterns.
02. MPV Design
With the foundation clear, we moved on to shaping the MVP. We focused on how the platform feels from the very first step, starting from the website and sign-in and continuing into the main console modules. Every screen had to tell one story: fast orientation, clear data, no wasted motion.
With the foundation clear, we moved on to shaping the MVP. We focused on how the platform feels from the very first step, starting from the website and sign-in and continuing into the main console modules. Every screen had to tell one story: fast orientation, clear data, no wasted motion.
Landing Page
Alongside the console, we built the Mozverse website — the first touchpoint of the ecosystem. It introduced what Mozverse stands for, outlined its core products, and guided developers directly into the Console.
Alongside the console, we built the Mozverse website — the first touchpoint of the ecosystem. It introduced what Mozverse stands for, outlined its core products, and guided developers directly into the Console.
Simple Start
We kept authentication as lightweight as possible, with a single-step login and signup that let developers in fast and without friction. This simple flow proved more effective in tests, reducing drop-offs and giving a smoother first impression.
We kept authentication as lightweight as possible, with a single-step login and signup that let developers in fast and without friction. This simple flow proved more effective in tests, reducing drop-offs and giving a smoother first impression.
NFT API Page
From early developer interviews, we learned that speed, clarity, and consistency mattered most. Developers needed to access data, logs, and network activity without friction.
To validate our design direction, we ran an A/B test for the NFT API page, as for the first core module defining how complex blockchain data should be presented.
From early developer interviews, we learned that speed, clarity, and consistency mattered most. Developers needed to access data, logs, and network activity without friction.
To validate our design direction, we ran an A/B test for the NFT API page, as for the first core module defining how complex blockchain data should be presented.
Version A followed a clean, monochrome layout focused on simplicity and structure.
Version A followed a clean, monochrome layout focused on simplicity and structure.
Version B added stronger visual hierarchy and subtle color cues to highlight states and metrics.
Version B added stronger visual hierarchy and subtle color cues to highlight states and metrics.
After testing with developers, Version B performed better: participants could identify key data faster, distinguish request statuses more easily, and navigate the interface with less cognitive load.
This version became the visual foundation for all future analytics modules.
After testing with developers, Version B performed better: participants could identify key data faster, distinguish request statuses more easily, and navigate the interface with less cognitive load.
This version became the visual foundation for all future analytics modules.
Ultranode Page
Next, we designed the Ultranode page, the main gateway for working with live blockchain data. It connects developers to multiple networks (Ethereum, Polygon, Arbitrum) through a unified API.
Our goal was to make monitoring effortless: key metrics like throughput, latency, and network status are now clear and instantly readable, without extra setup.
Next, we designed the Ultranode page, the main gateway for working with live blockchain data. It connects developers to multiple networks (Ethereum, Polygon, Arbitrum) through a unified API.
Our goal was to make monitoring effortless: key metrics like throughput, latency, and network status are now clear and instantly readable, without extra setup.
IPFS Page
Then we designed the IPFS interface, a module for decentralized file storage and management. Developers can upload, pin, and retrieve files through a simple CID-based system, with clear stats on usage and performance.
We shaped the experience to feel as intuitive as a cloud drive, but with the transparency and resilience of Web3 underneath.
Then we designed the IPFS interface, a module for decentralized file storage and management. Developers can upload, pin, and retrieve files through a simple CID-based system, with clear stats on usage and performance.
We shaped the experience to feel as intuitive as a cloud drive, but with the transparency and resilience of Web3 underneath.
Dashboard Page
We then focused on the Dashboard, the first screen developers see when opening the Console. It helps users get started, offering clear entry points for NFT API, IPFS, and Ultranode, and later becomes a live summary of their activity.
Each section gives a quick pulse of key metrics like request volume, success rate, and response time, offering a clear overview before diving into the detailed module views.
We then focused on the Dashboard, the first screen developers see when opening the Console. It helps users get started, offering clear entry points for NFT API, IPFS, and Ultranode, and later becomes a live summary of their activity.
Each section gives a quick pulse of key metrics like request volume, success rate, and response time, offering a clear overview before diving into the detailed module views.
03. Developer Tools
With the data and infrastructure layers defined, we turned to the operational side, focusing on tools for building requests, tracking transactions, and managing users.
With the data and infrastructure layers defined, we turned to the operational side, focusing on tools for building requests, tracking transactions, and managing users.
Request Builder
The Request Builder helps developers build and test API requests directly inside the Console without the need for external tools, so you can create, send, and validate requests, see real-time responses, and debug instantly.
We redesigned its visual hierarchy and brought it in line with the rest of the product, creating a clearer, more consistent experience. The structure remained familiar, but became easier to scan and navigate.
The Request Builder helps developers build and test API requests directly inside the Console without the need for external tools, so you can create, send, and validate requests, see real-time responses, and debug instantly.
We redesigned its visual hierarchy and brought it in line with the rest of the product, creating a clearer, more consistent experience. The structure remained familiar, but became easier to scan and navigate.
Nodifier
Another screen we redesigned was Nodifier, a tool that lets developers subscribe to real-time blockchain events, from mined or dropped transactions to NFT and collection activity, using webhooks.
We refined its hierarchy and visual rhythm to match the rest of the Console, making event types, statuses, and actions easier to scan and manage.
Another screen we redesigned was Nodifier, a tool that lets developers subscribe to real-time blockchain events, from mined or dropped transactions to NFT and collection activity, using webhooks.
We refined its hierarchy and visual rhythm to match the rest of the Console, making event types, statuses, and actions easier to scan and manage.
Super Admin
As the final step, we redesigned the Super Admin workspace, where administrators manage users, roles, and access across the platform.
The new layout combines user lists and detailed permission settings in one place, making it easier to review roles, toggle access, and adjust service rights without switching contexts.
As the final step, we redesigned the Super Admin workspace, where administrators manage users, roles, and access across the platform.
The new layout combines user lists and detailed permission settings in one place, making it easier to review roles, toggle access, and adjust service rights without switching contexts.
Mobile Version
We also adapted all key screens for mobile, allowing developers to monitor data and make requests from any device, anytime. The structure was simplified for smaller viewports while keeping the same clarity and flow as on desktop.
We also adapted all key screens for mobile, allowing developers to monitor data and make requests from any device, anytime. The structure was simplified for smaller viewports while keeping the same clarity and flow as on desktop.
06. Results and Impact
We transformed a raw alpha into a cohesive platform ready for daily developer use. Each module from Dashboard to Request Builder now followed a unified structure and visual language. Developers could monitor blockchain activity, test APIs, and manage data seamlessly across tools.
The MVP was delivered on schedule and helped Mozverse validate its product direction for the next phase. Because our development team also represented the target users, we iterated quickly, simplifying flows, improving hierarchy, and removing friction across the console.
A new design system became the foundation for scaling, enabling faster collaboration and consistent feature delivery.
We transformed a raw alpha into a cohesive platform ready for daily developer use. Each module from Dashboard to Request Builder now followed a unified structure and visual language. Developers could monitor blockchain activity, test APIs, and manage data seamlessly across tools.
The MVP was delivered on schedule and helped Mozverse validate its product direction for the next phase. Because our development team also represented the target users, we iterated quickly, simplifying flows, improving hierarchy, and removing friction across the console.
A new design system became the foundation for scaling, enabling faster collaboration and consistent feature delivery.
Key Outcomes
2X faster
2X faster
request testing
request testing
1.5X faster
1.5X faster
feature rollout
feature rollout
1 unified design system
1 unified design system
for future scaling
for future scaling
What I learned
This project taught me to design for developers, focus on speed, clarity, and how things work behind the surface.
I learned to run quick research and testing cycles, turning insights into real improvements fast, together with engineers and product leads.
This project taught me to design for developers, focus on speed, clarity, and how things work behind the surface.
I learned to run quick research and testing cycles, turning insights into real improvements fast, together with engineers and product leads.
Back to top
get in touch
bg.mavrin@gmail.com
connect on LinkedIn
Bogdan Mavrin