Ready SDK Documentation
Comment on page


Benefits & Use Cases

Feature Overview

Ready's proprietary crypto wallet provides a mobile app store-compliant & casual user-friendly solution for leveraging Web3 strategies in your game.
Ready's wallet is non-custodial, which translates to players maintaining exclusive control of their wallet. This also keeps things simple and familiar for players, no prior knowledge of Web3 is required since creation is managed simply by setting a password.
Some existing Web3 games require a wallet at the moment the game is launched, but for certain platforms or audiences, this might be a bit offputting to players looking to try a game for the first time. Ready's Wallet Module allows you to incorporate wallet creation at the time of your choosing, whether it's at launch or day 7.
The only time the wallet is required is when players are purchasing or claiming an NFT virtual item for the first time - giving you the flexibility to determine why, how, and when to prompt players to create a wallet.

Key Benefits

  1. 1.
    Mobile App Store Compliant: Ready's SDK allows you to integrate Web3 on iOS and Android! Check the In-Game Implementation section for an example of a compliant NFT purchasing flow.
  2. 2.
    Casual User Friendly: It's not necessary for the player to be versed in Web3! They need only be versed in wanting to play your game or getting that awesome sword.
  3. 3.
    External Wallet Support: Players of course have the option to move their NFTs out of Ready's proprietary wallet, with Metamask being our initially supported option. More options will be added as players or developers request!
  4. 4.
    One-Time Setup: The wallet is associated with a player's Ready account. This means the player will only need to set up their wallet one time, in one game. After that, if they log in to another game in the ecosystem they will automatically have access to their wallet & be able to purchase or claim NFTs with no extra steps.

In-Game Implementation

Developers maintain the ability to determine the best place to trigger account & wallet creation - you know your player funnels best! However, platform-based regulations (in particular on Android and iOS) mean that in order to get your submission accepted you should follow an implementation like the flow shown below.
The flow below illustrates how a player can purchase an NFT in your game on a mobile platform. If a player has an account, a wallet, and enough currency, they complete their purchase normally. Checking for each of these states allows you to trigger the appropriate next step for players.
NFT Purchasing Flowchart with Wallet Creation and Account Creation Steps
Note that the above example includes a login panel with Apple/Google/Facebook sign-in options. Our updated SDK utilizes email and password to log in - see User Authentication for details.
In order for players to create a wallet in your game they'll need to set a password. You can trigger a pop-up like the one shown below to prompt players to do so. We recommend at a minimum requiring the player to enter the password twice and check that the entries match.
Create a Wallet Popup
For Web2 titles migrating to Web3, we do recommend keeping it simple like the above example - there were no significant issues with player onboarding in previous integrations that used this simple wallet creation method.
Depending on your audience you may choose to implement a bit more tutorialization, see the NFT Merchandising section of the Store guide for an example.