Internet Identity is a privacy-preserving sign-in system for ICP apps that lets people manage passkeys and OpenID-based accounts in one place. Users can create an identity from a compatible dapp or from the Internet Identity landing page, then add per-app accounts for personal, business, or testing, keeping contexts separate without sharing emails or passwords.
I ran usability tests on the existing journey—(1) creating an identity from a dapp, (2) adding an account within Internet Identity, and (3) creating a second identity—then synthesized findings into a themes-and-recommendations deck. After stakeholder review and prioritization, I redesigned the end-to-end flow with clearer copy, simpler steps, and stronger feedback to make the experience more user-friendly.
Role: Lead UI/UX Designer
Researcher
Brief
Internet Identity is a privacy-preserving sign-in system for ICP apps that lets people manage passkeys and OpenID-based accounts in one place. Users can create an identity from a compatible dapp or from the Internet Identity landing page, then add per-app accounts for personal, business, or testing; keeping contexts separate without sharing emails or passwords. The project aimed to identify pain point through usability testing and then to redesign the flows to improve usability, streamline sign in / sign up process , and support the new concept of internet identity and their accounts linked within a dapp.
Challenges Identified
Education & awareness: 1. Low trust and confusion about what Passkeys and Internet Identity are, how they work, and where data lives. 2. Gaps around privacy, recovery, decentralization, and Identity vs. Account concepts.
UX & flow improvements: 1. Ambiguity between Google and Passkey sign-in options. 2. “Use Existing Passkey” step caused drop-offs; lacked guidance. 3. Post-authentication, creating/choosing accounts wasn’t clear; weak success/feedback states and no obvious handoff to a control center. 4. Users encounter Internet Identity across third-party dapps/auth systems, so confusion often originates outside our UI.
Naming & management: 1. Duplicate names across identities/accounts; unclear primary naming. 2. No central place to rename, edit, delete, or manage multiple identities/accounts. 3. Terminology overlapped with dapp concepts, creating mental-model collisions.
Security & trust: 1. Unclear explanation of biometrics and on-device vs. cloud handling. 2. Needed to differentiate Internet Identity’s security model from providers like Google, while showing interoperability.
Approach
Usability tests on the “as-is” journey focusing on:
Creating an identity from a dapp,
Adding an account within Internet Identity,
Creating a second identity.
Synthesis & prioritization: Thematic analysis → findings deck with problem statements and recommended fixes.
Flow redesign: Clearer entry screens, progressive disclosures, streamlined steps, consistent confirmation and error patterns.
Copy & education: Plain-language microcopy, inline tooltips (seed phrase, passkeys, multi-account), and empty-state guidance.
Consistency & responsiveness: Unified patterns across desktop and mobile, with light/dark modes and accessible contrast.
Handoff & iteration: Prototype walkthroughs with stakeholders and devs; quick loops to align on technical constraints.
Updated Journey
RICE Scoring for Flow Prioritizations
Usability Testing - Rainbow Methos
Outcomes
Education: Plain-language guides/FAQs/tooltips clarified Passkeys, privacy, recovery, and Identity vs Account.
UX/Flow: Clear Google vs Passkey choice; split Create Identity vs Create Account; improved “Use Existing Passkey”; simpler CTAs; success messages with dashboard links.
Naming/Management: Enforced unique names with light metadata; central dashboard for rename/edit/delete; terminology aligned to mental models.
Security/Trust: Explained biometrics and on-device vs cloud storage; distinguished our security model from Google; surfaced recovery options.
Impact: Fewer errors, smoother cross-dapp switching, and a scalable UI with modular components and a new dashboard.