Flutter
With AppKit Flutter, you can easily let people interact with multiple EVM compatible wallets and blockchains.
Let’s get started with the installation and configuration!
Installation
If you are just starting a new project, you can use our CLI tool to get started quickly.
-
- Add
reown_appkit
as dependency in yourpubspec.yaml
and runflutter pub get
(check out the latest version) - Or simply run
flutter pub add reown_appkit
- Add
-
- Locate your
/ios/Podfile
file and add the following as the first line:
- Locate your
-
- Run
$ pod install
inside/ios
folder.
- Run
-
- You should now be able to run your app with
flutter run --dart-define=PROJECT_ID={your_project_id}
- You should now be able to run your app with
Enable Installed Wallet Detection
To enable AppKit to detect installed wallets on the device, you need to make specific changes to the native sides of the project.
- Open your
Info.plist
file. - Locate the
<key>LSApplicationQueriesSchemes</key>
section. - Add the desired wallet schemes as string entries within the
<array>
. These schemes represent the wallets you want to detect. - Refer to our Info.plist example file for a detailed illustration.
Example:
- Open your
Info.plist
file. - Locate the
<key>LSApplicationQueriesSchemes</key>
section. - Add the desired wallet schemes as string entries within the
<array>
. These schemes represent the wallets you want to detect. - Refer to our Info.plist example file for a detailed illustration.
Example:
- Open your
AndroidManifest.xml
file. - Add your
<queries>...</queries>
schemes outside of<application />
scope. - Refer to Android Specs for more information.
Example:
Coinbase Wallet support
Coinbase Wallet does not use the WalletConnect protocol for communication between the dApp and the wallet.
This means that pairing topic, session topic, session events and other session-related features are not available when connecting to Coinbase Wallet.
However, you can still enable it to seamlessly connect with your dApp with these additional steps.
If you still want to support it, on your iOS and Android native side make the following changes:
- Open your
Info.plist
file. - Locate the
<key>LSApplicationQueriesSchemes</key>
section. - Include
<string>cbwallet</string>
scheme as mentioned above in previous section
Example:
- Make sure pods are installed, otherwise run
pod install
inside your/ios
folder. - Open your
/ios/Runner.xcworkspace
file with Xcode and add the following code inAppDelegate.swift
file:
Checkout out the AppDelegate.swift file from our sample dapp for reference.
- Open your
Info.plist
file. - Locate the
<key>LSApplicationQueriesSchemes</key>
section. - Include
<string>cbwallet</string>
scheme as mentioned above in previous section
Example:
- Make sure pods are installed, otherwise run
pod install
inside your/ios
folder. - Open your
/ios/Runner.xcworkspace
file with Xcode and add the following code inAppDelegate.swift
file:
Checkout out the AppDelegate.swift file from our sample dapp for reference.
- Open your
AndroidManifest.xml
file. - Add
<package android:name="org.toshi"/>
scheme inside<queries>...</queries>
as mentioned above in previous section
Example:
Disable Coinbase Wallet
Coinbase Wallet is enabled by default even if, in order to function properly, a few steps has to be done as described in the previous section. However, if you don’t want to include/support Coinbase Wallet on your app you just need to pass Coinbase Wallet id fd20dc426fb37566d803205b19bbc1d4096b248ac04548e3cfb6b3a38bd033aa
to excludedWalletIds options Array.
Phantom Wallet support
Phantom Wallet support is available from reown_appkit: ^1.4.0
.
Phantom Wallet does not use the WalletConnect protocol for communication between the dApp and the wallet, instead it provides an internal API mechanism based on deep/universal links.
This means that pairing topic, session topic, session events and other session-related features are not available when connecting to Phantom Wallet and the interaction is really basic. Dapp sends a request, Phantom Wallet responds. That’s all.
Furthermore, Phantom Wallet’s deep/universal linking mechanism supports interaction exclusively with the Solana network. This means that if you have EVM networks configured in your AppKit instance, they will not be available for use after connecting with Phantom.
In order to support Phantom Wallet interactions a few extra steps has to be performed (only if you haven’t implemented Link Mode already).
- First, be sure you already have your redirection back property configure in your dApp’s metadata. See Redirect to your dApp
- Then you will have to implement your own Deep Link mechanism on Flutter (and native) side so when a link is received through it, you would just call
await _appKitModal.dispatchEnvelope(link);
As a guidance, here you can see how it’s done in our sample dApp:
First, on Flutter side we create an EventChannel
where links are going to be received and passed to dispatchEnvelope()
.
Then, on both native sides we leverage native APIs to capture the app opening link and send it to Flutter side.
Links to full examples:
- Android’s platform specific code (only
eventsChannel
is important Phantom wise) - iOS’s platform specific code (only
eventsChannel
is important Phantom wise) - Dart’s specific code (only
eventsChannel
is important Phantom wise)
Constructing a Solana transaction would depend on the library/package of your choice but in our sample dApp’s code you can see how we do it using solana_web3
package.
Disable Phantom Wallet
Phantom Wallet is enabled by default even if, in order to function properly, a few steps has to be done as described in the previous section. However, if you don’t want to include/support Phantom Wallet on your app you just need to pass Phantom Wallet id a797aa35c0fadbfc1a53e7f675162ed5226968b44a19ee3d24385c64d1d3c393
to excludedWalletIds options Array.
Example
AppKit with Flutter example
Check the Flutter example
Test Apps
Want to see AppKit in action? Download our sample AppKit apps below and explore what it can do. Enjoy! 😊
Was this page helpful?