Discarded Approach

Our initial approach prioritized security over the task itself, making it difficult for users to understand the context behind the approvals.

Improved Approach

Improved Approach

A context-aware, checkout experience that helps users clearly understand what they're approving, what actions are required, and the expected outcome.

Complex Situations

What happens when the backend can support advanced functionality, but the limited viewport makes it difficult to present that complexity?

Our backend can detect wallets that share the same password, allowing users to authenticate multiple wallets with a single password entry. This was a critical capability, as many institutional users manage dozens of wallets—entering the same password 50 times would be unnecessarily repetitive. The behavior ultimately depends on how each user chooses to secure their wallets, whether with shared or unique passwords.

I explored several design iterations to balance efficiency with clarity. While I wanted to avoid introducing unnecessary steps, processing everything at once could also leave users uncertain about what had happened, especially when some wallets required different passwords.

Solutions Provided:

1. Although the authentication happens instantly, I introduced a loading animation to clearly communicate which wallets were successfully authenticated.
2. Added a second animation to show how many wallets had been processed and identify which wallets still required a password.
3. Designed a dynamic input field that clearly communicates the next required action based on the user's progress..

Product Exploration

Pitched the idea of users having a distress code that discreetly triggers an emergency protocol, securely transferring funds to a backup wallet while temporarily locking down the enterprise.