Hello! Reporting back from the subgroup on Language, Education, and Explanations.
A mom who needs a way to buy a Kollectible Kat for her daughter because she wants her daughter to be in tech / ready for the next big "thing".
* Unfamiliarity with Ethereum transaction process
* Temptation to repeat transaction while waiting for initial transaction to complete
* Unclear / potentially confusing messaging about transaction status
* Not knowing "what happens next" when some (possibly ambiguous) step will be irreversible
* Not know what will and won't be public information (embedded in blockchain) permanently
* Not knowing exactly when item in question has been delivered / claimed
Web 2.0 transaction process is a clear pattern:
* Checkout (terms of agreement)
* Consumer verification
* Vendor verification
Many of us are so comfortable with this flow that we simply disregard Vendor verification (e.g. Order confirmed pages), but in Web 3 context most confusion arises from transaction initiation through delivery.
We introduce the Web 3 Transaction flow. Instead of splitting the order process into three distinct steps as in Web 2.0, we open a dialogue with users from the initiation of transaction through the delivery confirmation.
Steps in flow:
1. User adds item to cart
2. On Transaction Flow page, in addition to listing items for purchase, we message to the user what is about to happen, such as # of confirmations needed or an estimated time to delivery. At this step, the user signs the transaction
3. At this point, the wallet / extension presents user with transaction dialog (payment, gas cost)
4. Next the user enters confirm screen and confirms the transaction, initiating blockchain processes
5. The user returns to the Transaction Flow page of the DApp which should ideally be maintained with live updates on blockchain status (e.g. Infura transaction API). Other helpful tools include a visual progress bar, animations to indicate progress. Users could be presented with randomized blockchain tips similar to Spotify details or video game load screens.
6. If a user chooses to navigate away from the Transaction Flow page, the Dapp should maintain a status indicator that indicates when the purchase has been delivered, or if any error has been encountered.
7. Once the transaction has completed, the Transaction Flow page should clearly indicate the purchase has been fulfilled. The Dapp might trigger a snackbar / toast notification at this time. The Dapp might also add that while the user now owns the Kollectible Kat, it may take a while for their favorite wallet / curation app to see it.