Three Months of a Small Site (3): Red for Up, or Green for Up?
Previous: More Than One Clock | Next: Moving House, and a Two-Month-Old Backup | 中文版:红涨绿跌,还是绿涨红跌
This post is about the interface, not the data. The site’s interface is simple, yet what changed most over these three months were the least noticeable parts.
Colour
In China, red means up and green means down. In the US and most overseas markets it is the other way round.
The site has users of both habits. Some watch the domestic market every day, where red is good news; others are used to overseas apps and tense up a little at a screen full of red.
I started with the Chinese convention and quickly got feedback. The fix was simple: let people choose. One switch in the settings, and every up/down colour on the web and the phone follows it.
It taught me something: colour isn’t decoration, it is language. The same colour says opposite things to different people. When something has no right answer, only habits, the best move is to hand the choice over.
Height
At the top of the home page is a row of small tiles showing a few market indicators. For a while they were uneven: a tile with an extra line of small print stood a bit taller, one with a short number a bit shorter.
Each tile on its own was fine; together they looked messy. Users never say “the tile heights are inconsistent”. They say “it looks a bit off”.
The fix was to make the row always the same height and leave space where there is less content. After the change nobody noticed anything, which is probably how you know it was right.
An error that wasn’t
The phone app has pull-to-refresh. For a while, people occasionally saw an error message while refreshing. Dismiss it, refresh again, and all was well.
It turned out they were refreshing too quickly: the previous refresh had not come back yet, they pulled again, and the app cancelled the earlier request. The system counts a cancellation as a kind of failure, so up popped an error.
But it wasn’t an error at all. The user changed their mind and the app did as asked. Once that case was quietly ignored, the message never appeared again.
What these problems share: the program’s view and the user’s view differ. The program thinks “a request failed”; the user thinks “I just refreshed, why are you complaining?”
One reassuring line
A tiny change: a line above the fund list saying “updated at such-and-such time”.
Before it, people sometimes asked, “Is this number current?” After it, almost nobody asked. The data didn’t change at all; people could simply see its time.
It is the same idea as “every number carries its time” from the last post, only this time for human eyes.
Takeaways
Most interface problems have no technical difficulty; the hard part is noticing them. A few lessons:
- Where cultures differ, give people the choice;
- Tidiness is information too;
- Something the user cancelled is not an error;
- Showing when data is from works better than insisting that it is accurate.
The next post is about moving house, and something I only discovered long after the move.
Comments