After creating your unique API Key, include a single JS file with your configuration settings and just initialize Assist.js on the first page of your Dapp. Then call the onboard() function to run your users through the setup process.
Want to see it live? Disable MetaMask (if you have it) and visit our demos below.
Keeping track of all of the possible user states is complex and error-prone. They change on the fly. Instead, free yourself – and your team – from this never-ending headache and hours of follow-on support work. Let us cover every nuance and edge case for you.
Since most Dapps aren’t designed for mobile, we’ll let users know if they must use a desktop browser to access the Dapp.
Not all browsers support Dapp transactions. We’ll see if their browser matches our list of supported Web3 Browsers. And if not, we’ll point them to one that is — and tell them where to install it.
Many new Dapp users don’t know what a wallet is. We’ll see if they’ve installed MetaMask and if not provide a link to where they can go install it.
After users install MetaMask, they’ll need to log in. We’ll show them exactly how.
Newer versions of web3 require users to grant access to your Dapp to interact with their wallet. We’ll see if that’s necessary, and help them complete this task.
If users aren’t connected to your specified network, we’ll show them how to change their network in MetaMask.
If your new users don’t have any ETH, we’ll direct them to an exchange where they can get ETH and transfer it to their MetaMask wallet.