A decentralised exchange that had to serve a first-time buyer and a professional developer on the same screen. Brand, architecture and a two-theme design system, built end to end.
Trust in decentralised finance is a design output, not a marketing claim. FiboDex earns it by making the first transaction understandable and the thousandth one fast.
FiboDex wanted one ecosystem for exchange, NFTs, in-game assets and tangible asset records, on its own chain. Every one of those products speaks a different language, and the platform had no shared one.
The audience splits hard: beginners who abandon at the first wallet dialog, and developers who leave if the tooling is shallow. Designing for the average of the two would have failed both.
Market data is unforgiving. Real numbers, real money, no room for a screen that looks calm but reads slowly.
The brand read as another generic crypto startup, so trust had to be designed before any dashboard could be believed.
Competitive teardown of exchanges and NFT marketplaces, eight 60-minute interviews across investors, developers and beginners, stakeholder alignment on the ecosystem scope.
Two primary personas, journey maps per persona, and an information architecture that separates trading, assets, developer tools and learning.
Brand identity built on a Fibonacci construction grid, user flows, wireframes, then a light and dark design system with documented components.
High-fidelity screens for onboarding, fast buy, trading, portfolio and profile, plus handoff documentation and social/brand applications.
The brief assumed one audience. The interviews showed three, with directly opposing definitions of a good platform. That contradiction became the design problem.
| Role | Tools used | Focus |
|---|---|---|
| Investors | Centralised exchanges, portfolio trackers | Real-time data, reliability, portfolio clarity |
| Developers | NFT tooling, smart-contract stacks | APIs, sandbox, documentation, deployment control |
| Beginners | Mobile banking, occasional crypto apps | Plain language, guided steps, safety |
“I want to dip my toes into blockchain investment, but it all seems overwhelming and complicated.”
“I need a platform that does not just cater to beginners but offers advanced tools and support for developers like me.”
Participants understood risk perfectly well. What stopped them was interface language: gas, slippage, custody, network. Every unfamiliar word was read as a possible way to lose money.
Design need · Plain-language labels first, technical terms available on demand, never the other way round.
Delayed or ambiguous numbers destroyed confidence faster than any visual flaw. Participants wanted to know when a figure was last updated and whether it was live.
Design need · Timestamped, clearly live market data with explicit states for stale and unavailable.
Developers and active traders described guided flows as friction. They wanted configurable dashboards, saved layouts and keyboard-speed access to order types.
Design need · Progressive disclosure that scales up, not just down: expert density as a deliberate mode.
Multi-factor authentication, session logs and transparent transaction records were treated as table stakes. Users wanted to see the protection, not read about it.
Design need · Security surfaces inside the product, in the profile and confirmation flows.
API access, a sandbox environment and worked examples were the deciding factors in whether a developer would build on FiboDex at all.
Design need · A developer area treated as a product, not a footer link.
Tutorials in a separate help site were never opened. Participants wanted the glossary at the moment of the unfamiliar word.
Design need · Inline learning: contextual definitions, then a knowledge base for depth.
Discover and define ran wide across all four product lines before anything was drawn. Develop and deliver narrowed to the two journeys that carry the business: a beginner's first purchase and a developer's first deployment.
Emma needs to buy her first token without feeling exposed. Leo needs to list, monitor and debug NFT projects. Rather than averaging them, the interface layers: a guided surface on top, full depth one step beneath it.
The developer journey exposed where the platform loses credibility: unclear documentation at onboarding and no visibility into listed NFTs during usage. Both became architecture requirements, not backlog items.
The mark is an isometric F constructed on a Fibonacci grid, with a blockchain lattice as its texture. Green for growth and trust, purple for innovation and ambition. The construction is literal so the story survives explanation.
Trading, asset management, developer tools and the learning centre each own a top-level branch. Cross-links are deliberate: a token in the portfolio links to its market, an unfamiliar term links to the glossary.
The account flow was designed around what goes wrong: wrong password, no account, network choice, unverified email. Every dead end has a labelled way out, because in finance a confused user assumes theft.
Fast Buy and the full trading module are the same product at two depths. Beginners never see order types they cannot use; advanced users reach them in one action, with no beginner wrapper to dismiss.
Tabular figures, aligned decimals, a fixed set of change colours and a defined stale state came first. In a data-intensive product the type scale for numerals is the design system's backbone.
Both themes were tokenised together, with contrast checked on the same components. Dark mode is where traders actually sit, so it could not be a late inversion of the light palette.
Glossary definitions appear at the term, in context, and link out to the knowledge base for depth. The separate tutorial site pattern was rejected: interviews showed nobody leaves a transaction to read.
Verification level, two-factor state and device history are shown as plain statuses in the profile, and confirmations restate what is about to happen in human language before it is signed.
Components, states, spacing and usage rules were documented so the developer team could extend the platform without inventing a fifth table style.
Persona and journey work was reviewed with stakeholders and industry experts against the eight interviews, so priorities traced back to evidence rather than opinion.
Flows were walked task by task with beginner and developer participants: create an account, make a first purchase, find a definition, list an NFT.
Both themes were checked for contrast and numeric legibility on the same components before handoff.
The design system was handed over with documentation so consistency is verifiable at build time, not negotiated per feature.
One identity and one component language now cover exchange, NFT store, game assets and developer tooling.
Beginners get a guided fast-buy path; advanced users get depth without the beginner scaffolding in the way.
Dark mode is a first-class theme, not an inverted afterthought: contrast and numeric legibility were specified per token.
The strongest decision was refusing the compromise interface. Two clearly served audiences beat one blended one, and layering made that affordable.
Brand and product had to be designed together. A trustworthy dashboard inside an untrustworthy identity still reads as risk.
If I ran it again I would instrument the first-purchase funnel from day one; the qualitative signal was strong but drop-off numbers would have settled several arguments faster.
Working across four product lines taught me to design the architecture as the contract. Once the branches were agreed, individual screens stopped being debated in isolation.
I'm available for product design roles and consulting projects.
contact@lidatohidi.com
