You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a UX designer, I recently became aware of a small UX problem. We talked about this briefly last week in Prague @benma
Users entering the Receive screen (where new addresses can be generated) often mistake the placeholder image for a real QR code.
To avoid misunderstandings, I suggest replacing this image with another image that is clearly illustrative. My first idea would be something that communicates in a concrete way that a new address can be generated in this screen. Perhaps an image that communicates a brand new receiving box would be appropriate.
Do you think this is a good idea?
If so, I would like to have the specifications for the image (dimensions and preferred file format).
After that I would follow up with more polished and concrete image suggestions.
The text was updated successfully, but these errors were encountered:
@paulosacramento thanks for the feedback. Yes, we aware some users found the placeholder QR code confusing and have some ideas on how to improve the whole workflow. Thanks for the input.
As a UX designer, I recently became aware of a small UX problem. We talked about this briefly last week in Prague @benma
Users entering the Receive screen (where new addresses can be generated) often mistake the placeholder image for a real QR code.
To avoid misunderstandings, I suggest replacing this image with another image that is clearly illustrative. My first idea would be something that communicates in a concrete way that a new address can be generated in this screen. Perhaps an image that communicates a brand new receiving box would be appropriate.
Do you think this is a good idea?
If so, I would like to have the specifications for the image (dimensions and preferred file format).
After that I would follow up with more polished and concrete image suggestions.
The text was updated successfully, but these errors were encountered: