Developing on the EOSIO blockchain meant jumping between multiple disconnected tools — one for inspecting blocks, another for managing accounts, another for testing transactions. EOSIO Explorer brought all of it into a single, unified interface: a developer tool that made building, testing, and debugging on EOSIO significantly faster and more accessible.
Client
Role
Product Design Visual Design Art Direction UX Research
Industries
Blockchain
Date
2019
Role & Team
Senior UX/UI Designer, responsible for information architecture, interaction design, visual design, prototyping, and usability testing. I collaborated closely with a Business Analyst at Block.one throughout the project.
Project Goal
Unify the fragmented EOSIO development workflow. Reduce the context-switching that slowed developers down, and make the platform accessible to developers at different levels of EOSIO experience — not just those who already knew their way around the codebase.
Design Process
The design process centred on understanding how developers actually worked — what they needed to see at each stage, where they were likely to make mistakes, and what made the existing fragmented tooling frustrating. From those insights, I structured the information architecture around the natural workflow: explore blocks, manage accounts, test transactions, deploy contracts. Each section was designed to feel logically connected, so developers could move fluidly between tasks rather than switching mental contexts with every action. Early prototyping and usability validation were used to test core workflows before development started — catching friction points in account management, contract deployment, and transaction testing early, when changes were still cheap.
Project Learnings
Developer tools require a different design mindset than consumer products. The goal isn't delight — it's efficiency and accuracy. A small piece of friction that barely registers in a consumer app becomes a serious problem when a developer is running the same workflow dozens of times a day. This project reinforced how much information architecture and interaction design matter in technical products, and how designing for varying levels of expertise requires different layers of the same interface to serve both beginners and power users well.