🎯 Goals and concepts
On Seed the user has control and sovereignty on their content.
Control = private digital key to sign content with cryptography without sharing their identity on any site.
This is easy until you want to use Seed on multiple devices and the key needs to work on all > multi-devices.
🔐 But, what is the vault?
It is a folder/ safe box where you have all your keys. It protects the digital key that you use to sign.
Vault can be moved
Seed can not have access to user's vault
The passkey is the key unlocks the vault.
The URL for the vault is hyper.media/vault
🖵 3 main scenarios
1. A new user creates an account and is ask to create key
2. An existing user needs to add key to the vault.
There is a user with the app installed
"Hey we have this new functionality to protect your account and take control, do you want to sync your keys across devices? If yes=
Sign in > I have an account
Import keys
3. As user wants to manage their vault and account settings
🙇🏽♀️ UX challenge
Why is important to do it right?
Even if this vault technology is really cool, if it feels confusing or too technical, users may leave before they see the value.
Keep it human, focus on control and benefits, and introduce complexity only when needed.
Some basics to have in mind:
Explain the benefit first: “You control of your content.” Avoid leading with how the vault works.
Use familiar metaphors like a “digital wallet” or “safe” instead of a “vault system” or “identity layer.”
Replace technical terms that can scare users with plain language: “Authentication” → “Confirm it’s you”
Guide with simple, contextual steps
Reinforce control and safety: Continuously remind users: “You can change this anytime”
Use visuals over explanations: Icons, toggles, and simple diagrams communicate faster than paragraphs.
Add microcopy where it matters: Small helper text near actions reduces doubt at key moments.
Do you like what you are reading?. Subscribe to receive updates.
Unsubscribe anytime