Request by sending an email to developer@vatom.com
There are a variety ways for you to use the Vatom Wallet in your own applications and customer engagement campaigns. You can even use Vatom modules to customize your own branded wallet experience.
If your goal is to build a customized wallet, you can get the job done with either Experience Kit or Wallet SDK. The core difference is whether you choose to embed your customizations within the Vatom Wallet app or prefer to embed a wallet inventory view within an app of your own. The best approach depends on which wallet features versus customizations are required. Consider the following chart:
Experience Kit | Wallet SDK | |
---|---|---|
Embedding | micro-site embedded in wallet | wallet inventory view embedded in custom app |
Overall Effort | basic micro-site is easy to build | more work to build app to contain everything |
Control | a fixed UI contains the micro-site | the encompassing app is up to the developer |
Wallet UI Options | maps & AR in addition to token inventory | limited to inventory view within iframe |
Library Features | data access features built in | limited additional data access via Identity SDK |
By default, Wallet SDK handles user login automatically when required. Most developers, pair WalletSDK with IdentitySDK to gain control over when the user's access token, the user's profile, and when the login process takes place.
If you are not sure whether you will require this additional control, it is reasonable to begin developing your app with just the Wallet SDK. The Identity SDK can added later if it becomes clearly necessary.