BitShares Deposit/Withdraw Engine upgradesteemCreated with Sketch.

in bitshares •  7 years ago  (edited)

The #BitShares user base is growing quickly and we have to prepare for many additional businesses and transfer providers that will join the ecosystem.

If you are familiar with the BitShares reference client you might get used on how to deposit, withdraw and send funds on- and off-chain, hereafter called the DW-Engine. But new users often struggle to understand how to use the DW-Engine and the result is many questions and complaints raised in the community channels.
Therefor I recommend to upgrade the DW-Engine and simplify all procedures as far as possible.

To begin with I would suggest to get rid of the separate "SEND" menu and merge the send and withdraw function in a single Menu.

Menu

Deposit/Withdraw

Submenu

Deposit
Withdraw->choose between send and withdraw
Custom->Legacy DW-Engine provided by transfer providers, also for FIAT etc.

High-Level

  • Merge send and withdraw function
  • Guide the user through the process
  • Display only required fields and options

Mid-Level

  • Choose between deposit and withdraw or custom
  • Select a token
  • Enter amount
  • Choose between on/off-chain
  • Select transfer-provider (optional)
  • Enter recipient (send/withdraw)
  • Enter memo (send/withdraw)
  • Switch fee token (optional)
  • Custom service provider (custom/legacy DW engine)

Detail-Level

  • see process diagram

To make the DW-Engine smart enough a small database/table is required to host and maintain the required transfer-provider information. The table could be embedded in the client itself or if possible could be hosted on github repository for realtime updates(if approved by n devs).

  • Token
  • Name
  • Symbol
  • Provider
  • URL

I am not a developer nor a designer but I've created a couple of mockup screens for Deposit, Withdraw and Send as well as a process diagram to visualize how the procedures could be built to match the mockup screens.
This github issue is only for the DW-Engine, other visible mockup design elements or colors are not part of my suggestion.

DEPOSIT Screen
DEPOSIT example

SEND Screen
SEND example

WITHDRAW Screen
WITHDRAW example

CUSTOM Screen
CUSTOM example for legacy DW-Engine and FIAT operations

DW-Engine_process_diagram
DW-Engine process diagram

Transfer_Provider_Information_example
Transfer-Provider-Information example table required for the automatic token to transfer-provider enumeration

Even if my mockup's may be to complex I hope we can at least use some parts to make the DW-Engine more comfortable.

This proposal has been published in github here: https://github.com/bitshares/bitshares-ui/issues/296

If you like this post please Upvote and Resteem.

Thank you and good luck
Follow @btswolf | steemit_button.png| btswolf_button.png| Telegram|bitsharestalk.org| Hangout friday's @1pm UTC| Documentation

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Excellent! Can Bill Butler do this as part of his current worker? If not, I will happily vote for a new worker to get his done

I think this would make the whole experience a LOT better. I'd like to test your proposal!

Good idea to think on a better solution to present and manage the SEND & WITHDRAW functions that do get confused by numerous users.

  ·  7 years ago Reveal Comment
  ·  7 years ago Reveal Comment