nexia

Identity Wallet

Self-initiated exploration of decentralized digital identity for three user types: individuals managing their credentials, organizations verifying identity attributes, and developers integrating verification into their products. The project investigates how granular permission control can be made legible and actionable without exposing blockchain complexity to end users.

Type:

Concept Project

Role:

Product Designer

Duration:

3 weeks and half

View prototype

view design system

man using MacBook

What I've designed

End-to-end information architecture covering three distinct spaces: identity (verified attributes), permissions (active connections with organizations), and audit (immutable event history)

User flows for granting, managing, and revoking granular permissions — including asynchronous on-chain states modeled as non-blocking interactions with explicit intermediate feedback.

Permission management UI with a full state taxonomy (active, expiring, expired, revoked, pending, suspended) and a conflict-of-interest model resolving competing needs across the three user types.

Component library covering core states for the Permission Card, Attribute Disclosure, and Transaction Status components, including error, empty, and loading states.

Visual system with semantic design tokens distinguishing permission states, credential trust levels, and action types — including a deliberate separation between destructive and irreversible actions.

Tools

What I've learned

Designing for three user types with partially conflicting needs — particularly around transparency vs. privacy — required resolving those conflicts at the architecture level before touching the interface. Decisions made in the data model directly constrained what was possible to design.

Keep reading…

Designing for three user types with partially conflicting needs — particularly around transparency vs. privacy — required resolving those conflicts at the architecture level before touching the interface. Decisions made in the data model directly constrained what was possible to design.

DESIGN ENGINEERING

DESIGN ENGINEERING

Connect to Content

Add layers or components to swipe between.

Let's talk and build a big project

I bridge the gap between design intent and engineering execution. Here’show systematic thinking applies to both sides.

Resume

LinkedIn

JD Albarran

© 2026, José David Albarrán V. Professional portfolio

I know what the tradeoffs are. Then I make the call.

My socials

JD Albarran

© 2026, José David Albarrán V.
Professional portfolio

Design that hols up
when the product grows.

My socials

JD Albarran

© 2026, José David Albarrán V. Professional portfolio

I know what the tradeoffs are. Then I make the call.

My socials