Turn technical infrastructure into clear operating decisions.
Lead UX/UI design
Onboarding · Dashboard · Node management
Design case study
Original DataHive interface · New portfolio composition
The original website uses movement to introduce the data platform and explain the relationships between its nodes.
DataHive brings personal-data control, identity checks, wallets and network participation together. People need to know what they are choosing, what is ready and what still requires their attention.
I led web and mobile UX/UI across onboarding, dashboards, node management, consent and data-permission flows, alongside the visual language.
Technical specifications and payment requirements must stay inspectable without overwhelming the main task.
Inside the original workThe original screens expose verification states, comparable node specifications, wallet/manual payment choices and activation states.
A closer reading of the original work: the problem each choice addresses and the value it is intended to create.
Identity, selfie, address, mobile and legal steps each have their own state.
Separate dashboard exploration from verification, and make outstanding requirements visible.
Help people understand the next requirement without losing their place in the product.
Node families share CPU, RAM, storage, yearly-fee and staking information.
Align the specifications, then move through quantity, cart and a clear payment choice.
Support an informed selection before asking for a financial commitment.
The designs distinguish active, approval, activation and issue states beside operational metrics.
Keep state, bandwidth, uptime and resource usage attached to the relevant node.
Help an operator connect a signal to the node and action it concerns.
Select a stage to explore its purpose.
Show progress and outstanding requirements.
Portfolio journey map, reconstructed from the original onboarding and node-management designs.
The original product, presented at the level where its hierarchy and choices can be inspected.
Wallet choices sit beside an explanation of what a wallet is and how to get one, supporting both experienced and unfamiliar users.
The checklist distinguishes identity, proof-of-identity, selfie, address, phone and legal-agreement steps and shows which tasks need action.
The checkout dialog makes the selected token, discount code, yearly node fee and activation conditions visible before the payment action.
The original operating view and node catalogue connect two distinct tasks: managing the nodes already owned and comparing a new one before checkout.
Node state, resource usage and the surrounding navigation share one consistent workspace.
The original catalogue aligns CPU, RAM, storage and price across node options, with an add-to-cart action for each.
The complete originals behind this case study. Open a board to inspect the source presentation.
A new design proposal created for this portfolio. Explore the visual changes beside the original project.
New interface design proposal · Sample states · Interactive local prototype
A dedicated activation prompt separates a pending task from routine metrics.
A shared table aligns state, uptime, capacity and bandwidth across nodes.
Search, state filters and a focused detail panel make the proposal explorable.
A connected product-design system covering setup, node selection, checkout, activation and ongoing management across web and mobile.
A dashboard can surface every metric and still fail to explain the next action. The new exploration gives exceptions priority and leaves routine detail available in context.
The interface coverage is visible in the source work. Task-time or activation-rate improvements have not been verified.
These explanations and presentation layouts are newly prepared from the available original artifacts. The validation tasks are proposals, not research already completed.
Original project screens from my published design portfolio. This case focuses on the interface and my design contribution; it does not claim independently measured business results.
Building a Farcaster miniapp from interface to infrastructure.