Concordium Wallet Suite

Two crypto wallets, one design system, and the workflow to keep them coherent. A year of work across mobile and browser.

Concordium's wallets, one mobile, one a browser extension, are how people hold tokens and interact with the network. By the time I joined alongside the design lead, they'd been through enough hands that nothing quite matched anything else. Before I could redesign anything, I had to figure out what was actually there.

Years of decisions, none of them connected. The screens were mostly fine on their own; the problem was none of them knew about each other. Patterns existed in multiple flavours, type and colour drifted screen to screen, deprecated flows sat next to active ones with no way to tell them apart. Every new feature got negotiated with the chaos before anything could ship.

It started with mapping, not designing. The first weeks were untangling: every file, every flow, archiving the deprecated, naming the alive, drawing a map of the product as it actually existed rather than as anyone thought it did. Less glamorous than redesign, more important than it.

The system got built underneath while features kept shipping. Tokens, components, conventions, and a branching and versioning workflow for the design files, with the wallets as the live proof of concept. That system is its own story, covered in the CCD case study. Here it's the foundation everything else stands on.

Then the overhaul. Navigation rethought, scattered homepage tools pulled into one coherent menu, an unused discover feature removed, account and main menus rebuilt, type and colour and spacing aligned across hundreds of screens. Most of the work doesn't show in any single screenshot. It shows in the consistency between them.

One language, two platforms. Mobile is for daily use; the extension is for transactions tied to a desktop session, like signing into a dApp. Forcing them to look identical would have made both worse. They share visual language, components, and primitives, but layouts diverge where the context demands it. Same wallet, two surfaces, coherent without being identical.

Both wallets now run on one system with consistent navigation, type, colour, and components across mobile and extension. The Figma files are organised, documented, and version-controlled, with a workflow that survives a designer joining or leaving.