2025/11 – Recent
Designed a cross-platform digital identity system for the governments, citizens, issuers, and verifiers.
This is a demo-based case study on an digital identity system. I partnered closely with PMs and engineers to turn identity infrastructure into usable product flows across app and console surfaces. My contribution covered research, fast hi-fi prototyping, interaction design, and ongoing solution shaping as technical constraints and government requirements evolved.
备注：由于这是面向国家政府的项目（哈萨克斯坦和巴基斯坦），只能展示Demo。界面中的文字皆为虚拟，不具真实参考价值。
Product
Digital Identity System
Scope
Citizen App (Mobile App),
Verifier System (Web App),
Issuer Console (PC),
Admin Console (PC)
Product Marketing Introduction
Timeline
1 month for a quick demo; product building WIP
Skills
Competitors Analysis · Information Architecture · Interactive prototyping
CHALLENGE
Multi-end System
This project explored a government-facing digital identity system built around verifiable credentials. The system needed to support multiple actors across one trust infrastructure: citizens collecting and presenting credentials, issuers reviewing and issuing them, verifiers requesting approved data, and a government super admin managing governance, schema access, and institutional trust.
Challenge
The UX challenge was not a single interface, but the coordination between all of them：
One action could trigger changes across multiple ends
Permissions and data access were too abstract for users to understand
In a trust-sensitive system, unclear status feedback could easily cause mistakes
COMPETITORS RESEARCH
Use ChatGPT to Understand
A Large Language Model is an ideal tool for understanding complex technical systems, as we have to analyze
Technical Research
Comprehensive Research
Cathy and I divided and conquered 14 different nations' national digital identity systems. We draw inspiration from the Bhutan, Ukraine, and UAW especially.
Research Document Menu
SIMPLIFIED USER FLOW
User-end Journey
Admin Console
Using AI to Visualize
Figma Make
PRODUCT HIGHLIGHTS
USER END
Present verifiable credentials to the verifier
ADMIN END
Super admin rotates admin's keys to protect data security
UI FOR MVP
A UI kit and component set for the MVP demo
PRODUCT MARKETING
Explain the data structure
PRODUCT MARKETING
Explain the use cases
Data Sync Design
Remove a Higher-level Admin can Trigger…
Because approvals made by higher-level admins affected issuers and schemas downstream, removing an admin was not just an account-management action. It raised a governance question: should previously approved entities remain valid, and how could the system preserve trust continuity without losing accountability?
Design with Technical Constraint
Edit -> Save Draft -> Publish Onchain
One challenge we ran into was that changes made in the admin console could not be treated like normal auto-saved SaaS edits. Some of these configurations had to be written on-chain before they were truly effective. That meant a user could finish editing in the UI, but the change was not yet live in the trust layer.
My design response was to make that unfinished state explicit through a persistent top-level notification and require an additional confirmation step before exit. Looking back, I think it was a good solution because it prevented false completion, although I’d further improve it by framing the interaction more clearly as draft vs. publish-on-chain.
