![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fpbs.twimg.com%2Fmedia%2FDP0M-Q-VAAEpHcp.jpg%3Alarge&t=665&c=BQCB-PHQKQxkGA)
I really like the initiative to change the look of the Digibyte wallet. However, I'd like to point out that the issues with the wallet go deeper than the colors. It is a common misconception that changing the UI to look more fancy, will increase the user's experience. The truth is that in order to achieve a meaningful and lasting impression on the user, the first step should be to think about the user. As obvious as that sounds, this simple fact is forgotten in 95% of the cases and therefore only 5% of UI updates are successful. I might actually be overstating the success rate.
Anyway, I'd like to point out some things to consider:
Who is the common user?
Who do you want to attract?
What does the user you want to attract want?
Currently you are making changes based on the wants of the current user, but not the needs of the current user. You're not making changes to appeal to new users, because they will see this and think it was always like this, and it is a bit confusing. Is it even safe?
What you want to do, is list the most important functions in the system and make them more visible. E.g.:
1. Available amount of DGB (blue on blue doesn't do it)
2. Send and receive
3. History (?)
4. ?
I'm not going to pretend I know what is most important, that comes from careful consideration and analysis.
Next, how do you create the best first impression? The user you want to attract wants to trust the wallet, this is really important in the long run, but also really difficult to achieve. You might want to do some banking UI competitor research.
The final thing: colors. Colors are only important once you've figured everything else out. The current approach assumes colors are what makes the UI good and starts from there, where as, the correct way is to finish with colors.
Now, these things only scratch the surface and real user friendliness comes from user research and understanding the needs and wants of the user. However, I understand that it might not be possible, in which case, your best bet would be to consult someone with expertise in the field. Personally I'd like to help, but I have no idea how to reach the people working on this.