Skip to content

[Docs] Embedded Wallets: clarify traditional vs embedded wallet in intro #2782

@bgravenorst

Description

@bgravenorst

Summary

Readers landing on Embedded Wallets should immediately understand how this product differs from a traditional self-custodial wallet (for example MetaMask as a browser extension). The intro currently moves too quickly before that mental model is clear.

  • New and non-Web3-native users may not know whether Embedded Wallets replaces MetaMask, competes with it, or complements it.
  • Without an upfront contrast, cognitive load stays high across multiple sections.

Proposed work

  1. Introduction (e.g. early in Get started): short explanation plus a scannable comparison (table or diagram) contrasting:

    • Traditional flow: install extension/app → create wallet → secure seed phrase → connect site → in-wallet approvals.
    • Embedded flow: stay in the app → sign in (e.g. email verification) → wallet usable in your integration with fewer steps.
  2. Cross-link to MetaMask Connect for teams whose users should keep using the extension.

Metadata

Metadata

Assignees

No one assigned

    Labels

    embedded walletsContent related to the embedded wallet content

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions