Case 02 of 05

One failure sent everyone back to step one. I made every request independent.

PRODUCT: Validator platform suite
ROLE: Senior Frontend UI Developer
YEARS: 2022–2024
USERS: Validators: technical node operators who jointly approve network changes
SCOPE: Request model, unified design language, implementation

Independentrequests: a failure affects only that one, instead of resetting everything.

3 → 1fragmented apps unified into one coherent interface, reusing most of the code.

Came backa year later, the client commissioned more work.

CONTEXT

A suite of web apps around a network and its platform. Validators, the technical operators who jointly approve changes to the network, use it to handle requests such as adding supported tokens, cross-layer transactions and changes to the validator set.

MY ROLE

Senior Frontend UI Developer. I worked from the client’s lead designer’s Figma files, and proposed, designed and pushed through the key UX changes myself.

THE CHALLENGE

A strict process that risked losing users’ work and data on any failure, spread across three apps that didn’t feel like one product.

What I didTwo edits to the plan

AChallenged the model

EXISTING FLOW

~~Struck out: A strict multi-step process, where any failure sends the user back to step one.~~

MY EDIT

Inserted: A dashboard where every request is an independent item with its own status, a “My tasks” queue for what needs your vote, and each validator’s approval tracked separately.

RESULT

A failure affects only that one request. I proposed it, iterated on it with the client’s lead designer, and built it.

BUnified the suite

EXISTING SETUP

~~Struck out: Three fragmented apps for validators, asset consolidation and liquid staking, without a coherent visual language.~~

MY EDIT

Inserted: One unified interface with a coherent design language and an easier journey, built so most of each app’s code could be reused.

RESULT

One product for users, with most of the existing code kept.

ALSO DELIVERED

Community submission portal
Technology showcase website
Game sites with leaderboards

About a year later the client came back and commissioned a website for their game-development technology. I built it, along with individual game sites with leaderboards.

OUTCOME

Validators no longer lose their work when a request fails, and the suite reads as one product. The client’s own tech leads rated me a strong senior developer, and they came back for more.

“He is savvy about both user and developer experience, and he challenges the client’s ideas and the status quo when it makes sense.”

— Engineering manager

NEXT CASE03 Embeddable checkout SDK