The new delegation framework answered several usability issues that end-users currently face in Web3: technicalities of confirmation dialogues, manual approvals, and more. Learn more about how I led the design for the new ERC-7715 standards.
MetaMask is working on a new offering to adopt ERC-7715 permission and ERC-4337 abstraction standards, which empowers web3 users with improved onboarding experiences, safer exchanges, and more agency.
ERC-7715 enables "enforced outcomes," ensuring that a transaction completes only if specific conditions are met. This revolutionary functionality could significantly reshape user interaction with smart contracts, bringing heightened security and control to Web3 users.
We aimed to give users the power to set enforced conditions on their transactions, allowing them to manage complex permission structures while abstracting away technicalities users don't need to know.
Beyond the design itself, it was critical to manage diverse stakeholders, communicate the project’s vision, and navigate technical complexities inherent to ERC-7715 (new permission standard) and its interaction with ERC-4337 (account abstraction).
(design featured in the talk below)
I began by conducting extensive sessions with key stakeholders across product, engineering, and leadership. Given the newness of ERC-7715, stakeholder inputs were essential in refining the user experience and in managing the high risk and unknowns.
Starting with lo-fi mockups, I explored ways to visualize “enforced outcomes” and help users understand transaction conditions.
Since the concept is very new to the ecosystem, early feedback sessions focused on usability and comprehension of ERC-7715 concepts:
As the designs progressed, I developed mid-fi and hi-fi mockups to bring more detail to the 7715 permission request screens.
Key screens, like the condition-setting UI, underwent several rounds of feedback and adjustments. Given the complexities of ERC-7715, each element had to balance clarity, value, understandability, and technical feasibility.
I created a series of rapid prototypes to showcase the end-to-end flows to be used in ongoing usability tests and internal feedback.
Why a high-fidelity prototype? This is a new, green-field way of permissioning across Web3. High-fidelity would allow us to better visually and interactively communicate concepts to research and feedback participants.
Implementation is currently underway to release a demo to the public. More on this soon.
A key constraint to note: This would be built the Portfolio repo, but would use confirmation components that existed in a separate repo.
This project was a unique challenge in combining pioneering technology with user-centered design. Leading the Web Wallet design for MetaMask highlighted the importance of bridging technical and user-centric insights to produce a valuable solution geared for adoption.