lisk-mobile
lisk-mobile copied to clipboard
Issues discovered in interoperable token usage features
Send token Objectives Review feedback
Send Token process
- Add Stepper component to Send Token process UI
- Change to black the color of
Picker
background mask - UI tweaks for Send Token process
- Make darker the "Select application" placeholder color (too light)
- Regular Inputs placeholders have too much font weight
- Fix Recipient rendering on Summary step based on input format. If user selects the Recipient, we need to display the user image and name, not only the address ID (depends on the way the user inputs the Recipient on the 1st step)
- Fix UI for very big input numbers (overflows). This includes: steps inputs, fee priorities and the send button on confirm password. Handle a max length
- Improve transaction submission message to a non-promising one (remove “confirmed in a matter of seconds” text). We do not know for certain if the posted transaction will get processed in seconds all the times. IMO it's better to just let the user know that we've posted the transaction and update them once the transaction is processed.
- Read token logos from API call response on applications and Tokens pickers. In the dropdown list, it would be visually nicer if the logos aligned vertically. Currently they follow the name of the chain which varies in length (number of characters). So, maybe left align the text and right align the logos or reorder to display the logos followed by the names?
- Change last step title to “Transaction Summary”.
- Fix close modal icons styles to adapt to UI.
- Change “use desktop” text to “Use Lisk Desktop’" for multisignature users screen.
- Make editable the sender account input on Send Token form. Users should be able to type it manually or select from list of options
- Disable “Continue” button on Send Token process for each step if any of the required fields are not filled
- Implement "Report the error via email” on the transaction failed screen of send Token process
- Add tooltips of “info” on Send Token form
- Add the hide message toggle button on Send Token form
- Disable FIAT conversion for non-LSK tokens on Send Token form. Only LSK tokens will have fiat conversion, once DEX implements conversion in 1.1 release we can integrate until then we just show the amount
- Send Token "To Application” input should be by default the same chain of “From Application” input (which is send tokens within app).
- Allow Send Token Amount input to be 0. User can send only memo with 0 amount (existing feature)
- Make Send Token priority input to be calculated based on network traffic (calculate dynamically by API request)
Request Token process
- Fix UI inconsistencies between Send Token and Request Token screens
- Add a “Request” button to click and open the QR code modal. Current UI is not so intuitive.