Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
worlddlckgh authored Oct 25, 2023
1 parent 0f5d97a commit 858f459
Showing 1 changed file with 13 additions and 13 deletions.
26 changes: 13 additions & 13 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,12 @@ Used by Jupiter and Meteora.
## Motives
Why not just use the existing wallet adapters?
- To bootstrap a dApp, we always find ourself doing the same thing over and over again, such as:
- notification when wallets are selected, connecting, connected, disconnected.
- auto reconnect to the last connected wallet
- mobile-first, responsive design
- themeing support
- Notification when wallets are selected, connecting, connected, disconnected.
- Auto reconnect to the last connected wallet
- Mobile-first, responsive design
- Themeing support
- Internationalization (i18n) support
- new user onboarding
- New user onboarding
- Built on-top of `@solana/wallet-adapter-base`, `@solana/wallet-adapter-react` and `@solana-mobile/wallet-adapter-mobile`, you are always welcomed to onboard or depart.

## Philosophy
Expand Down Expand Up @@ -82,14 +82,14 @@ export default ExampleBaseOnly;
- Why not ship with all wallets?
- Unnecessary bloat and bundle size on your dApp
- It's not sensible to always maintain an ever-growing list of wallets
- many existing wallets are not well maintained, often with unpatched security, or abandoned development
- lack of users
- does not support Versioned Transaction, severely limiting the adoption of many innovative functionalities of dApp.
- and hopefully, a gradually disappearing list of installed wallet adapter, as they migrate to wallet-standard

- why not ship with notification by default
- existing dApp might already have their own notification system
- checkout `src/components/examples/WalletNotification.tsx` for an example of how to use the notification system
- Many existing wallets are not well maintained, often with unpatched security, or abandoned development
- Lack of users
- Does not support Versioned Transaction, severely limiting the adoption of many innovative functionalities of dApp.
- And hopefully, a gradually disappearing list of installed wallet adapter, as they migrate to wallet-standard

- Why not ship with notification by default
- Existing dApp might already have their own notification system
- Checkout `src/components/examples/WalletNotification.tsx` for an example of how to use the notification system

- How to add/develop a new wallet?
- We recommend new developer develops Wallets that comforms to WalletStandard or MWA, to get instant discoverability.
Expand Down

0 comments on commit 858f459

Please sign in to comment.