AppKit enables passwordless Web3 onboarding and authentication, allowing your users interact with your application by creating a non-custodial wallet with just their emails or social accounts.

Remember to whitelist your dapp’s iOS’s bundleId and Android’s packageName in your cloud configuration.

  1. LogIn into https://cloud.reown.com
  2. Open Dashboard and scroll down to Mobile Application IDs menu
  3. Add your iOS Bundle ID and your Android Package Name

Email and Social login are supported only on EVM networks and Solana.

​
Integration

In order to support Email and Social Wallets creation just set featuresConfig: parameter in ReownAppKitModal initialization.

final _appKitModal = ReownAppKitModal(
  context: context,
  projectId: '{YOUR_PROJECT_ID}',
  metadata: const PairingMetadata(
    name: 'Example App',
    description: 'Example app description',
    url: 'https://example.com/',
    icons: ['https://example.com/logo.png'],
    redirect: Redirect(
      native: 'exampleapp://',
      universal: 'https://reown.com/exampleapp',
    ),
  ),
  featuresConfig: FeaturesConfig(
    email: true,
    socials: [
      AppKitSocialOption.Farcaster,
      AppKitSocialOption.X,
      AppKitSocialOption.Apple,
      AppKitSocialOption.Discord,
    ],
    showMainWallets: false,
  ),
);

​
Options

  • email bool : This boolean defines whether you want to enable email login. Default true
  • socials List<AppKitSocialOption> : This list contains the list of social platforms that you want to enable for user authentication. The platforms in the example include Farcaster, X, Discord. Is empty by default, it means that no social options is enabled.
  • showMainWallets bool_ : This boolean defines whether you want to show the main wallet options on the first connect screen. If this is false it will show a button that directs you to a new screen displaying all available wallets. Default true.

In order for Email Wallet to work properly, either AppKitModalConnectButton() or AppKitModalAccountButton() has to be instantiated during the whole lifetime of the app.

If you already use them then nothing else has to be done, but in case you don’t use them but still want to support Email & Social Wallets you would have to instantiate and hide them as follows:

AppKitModalConnectButton(
  appKit: _appKitModal,
  custom: SizedBox.shrink(), // Will make the button invisible
),
AppKitModalAccountButton(
  appKit: _appKitModal,
  custom: SizedBox.shrink(), // Will make the button invisible
),

​
User Flow

  1. Users will be able to connect to you application by simply using an email address. AppKit will send to them a One Time Password (OTP) to copy and paste in the modal, which will help to verify the user’s authenticity. This will create a non-custodial wallet for your user which will be available in any application that integrates AppKit and Email Wallets.

  2. Eventually the user can optionally choose to move from a non-custodial wallet to a self-custodial one by pressing “Upgrade Wallet” on AppKit. This will open the (Reown secure website) that will walk your user through the upgrading process.

Due to Safari’s strict third-party cookie policies, the SDK is not preserving sessions after the app is terminated (removed from memory). So upon app termination the user will have to re-authenticate themselves through a new OTP code if they want to sign. Our team is working to solve this issue soon.