Context & ownership
The asset is digital. The responsibility is shared.
Institutional custody is more than a balance and a transfer button. Teams need to create vaults, choose signing parties, set approval requirements and understand what happens after they submit a request.
I led UX architecture and cross-platform design-system development for io.vault. The work connected those financial workflows through consistent patterns across Web, iOS and Android.
A request submitted on the dashboard could still require approval from signing parties through the mobile app. Submission and completion needed to remain distinct.
Role, Scope & Team
My direct contribution
Led UX architecture and the cross-platform design system, establishing reusable components, interaction patterns and shared design foundations. Worked hands-on with engineering on UX decisions and component specifications.
The team I led
Managed two product designers, one focused on Web and one on iOS. The work shown here combines my hands-on contributions with their work under my design direction.
Cross-functional scope
Worked with product managers on requirements and direction; frontend and backend engineers on constraints and implementation; and the Head of Engineering, Marketing and Business Development on technical and business alignment.
Design decisions
Governance
Make signing power visible before the vault exists.
The vault-creation flow puts the threshold and signing parties in the same step. Each signer has an explicit signing weight, and the interface shows how the combined weight relates to the threshold.
The populated state also calls out when one signer has enough power to approve alone. That makes a consequence of the configuration visible at the point of decision.
Threshold, signing power and the consequence of that combination are shown together.
The threshold and signer pattern also has a narrow-layout specification.
Transaction structure
Carry the context through creation and review.
The transfer flow makes the source vault, network, destination, asset and amount explicit. An optional memo expands inside the form rather than creating another task.
A separate review step presents the request before submission. Handoff notes connect form spacing, the currency control and action styles to the design system, giving engineering concrete specifications alongside the flow.
The transfer form keeps the financial context alongside the action.
A separate review step makes room to check the request before submission.
Request inspection
Inspect the request without losing the activity context.
The activity table brings transaction descriptions, identifiers and lifecycle states into one view. A detail drawer opens alongside it, keeping the surrounding activity available while the request is inspected.
The drawer separates signing progress from transaction status, then groups the financial details below. Threshold progress and signer responses sit above the transaction ID, source, destination, amount, fees and total.
The activity table stays in context while the detail drawer brings signing progress and transaction facts together.
System architecture
A shared system, with room for each platform.
The system connects shared foundations, platform layouts and composite patterns for financial governance. The Web and iPhone handoff shows how the same approval model adapts to each platform.
Design → engineering
Lead the system. Stay close to the details.
The developer handoff combines responsive layouts, interaction states and component references. I worked with frontend and backend engineers to align these specifications with implementation constraints.
Outcome & reflection
A documented foundation for complex custody.
The work produced documented vault-creation and transfer flows, responsive layouts, approval states and reusable component specifications. The selected evidence shows how governance and financial actions could share a coherent interaction language.
A design system for custody has to explain responsibility as clearly as it defines controls. The threshold and pending-approval states are where that responsibility becomes visible.