Tag Info

New answers tagged

0

Take a cue from the social media widgets out there. Like/Follower/+1 etc buttons all need to show large numbers in a tiny little space.


0

My take is that the most valuable thing a tree does is this: Current thing Details of current thing More details More details... Another unrelated thing Its details Amazing details More details That is, it lets you see the detail of several different things at once. IMHO - this is not a very useful attribute. Most of the time, you get better UX by ...


1

Scientific notation would have you display this as: 1.23e5, it's more 'correct' when it comes to units: 1.23e5 m is right, whereas 123k m isn't (it should be 123 km). However if your users aren't comfortable with the 'k' postfix then I doubt they'd like this much, I merely mention it for completeness. Other possibilities might be to have something like: ...


8

Make the box big enough to contain any likely price. If your app has prices that might go up to six figures, make the price box big enough to take a six figure price. Do this even if you have to change the layout, even if real estate is limited and you have to sacrifice something else to make room for it. Don't use "K" or any other abbreviation to try to ...


-2

Auto re-size the numbers as the price grows; set one default size for the normal/expected price (2-3 digits let's say) and re-size it as needed.


29

Something which is done here in stackexchange is using colors in combination with k's to display weight (and I'm guessing m's as well). Look at how different colors represent different weight, in combination with the k's, you're receiving something which is unmistakably usable & understandable Reading further: Have you considered adding a ...


59

Best solution will be to increase the size of the box. If you can do it without changing the layout, it is good. For reducing the font size, I would suggest use a single size rather than going descending. It is easier to read. And, if you want to do 'k' representations, make sure the user has some way of accessing the actual number, via a tooltip or some ...


2

It's hard to say without knowing more, but here are some possible options: Make all boxes resize so they are all as large as the one containing the biggest number Reduce the padding to the left/right of larger numbers so they fit in the box Make the number text smaller Keep the 123K, and have the option of showing the full amount by some sort of toggle ...


7

Is the size of the box a limitation as was asked? The only reason I ask this is due to the fact that you can probably change the size of the box to the width of the largest price you have and set it as a fixed width for the box. Then center the price inside the box and you'll know that no other prices can exceed the width because you've buffered it using the ...


6

You could compromise on a mouse over for all digits (if that's an option), or you could make the trailing digits smaller / slimmer (if you have the resolution). I tried with Calibri + Arial narrow, this doesn't buy you much: (FWIW when using 'k' I'd use a small one, it distinguishes better from the digits and is SI-Correct. no such luck with 'M for ...


32

Your layout should support your content. First content, then appropriate layout. You can not easily break the physical constraints (like small screen), but maybe even your biggest number could be placed as separate line at smallest screen. Also I would recommend to keep in mind three stages concerning software: Useful (Functionality) Usable (Usability) ...


1

I agree with others here in that search and tags have replaced hierarchical conceptual models in many cases because they have real advantages both on the content creation side and the content consumption side. But I must point out that tree hierarchies are hardly obsolete as conceptual models that are surfaced in UIs. Often it is the right conceptual model ...


4

Perception: A new market for low complexity ("entertainy") applications has developed - explosively. Thus, even with non-diminishing tree use, it diminishes in percentage and plays less of a role in discusison of "modern" UI and UX changes. Alternatives: One feature of a hierarchy - fast locatability - has been largely replaced by instant search. We now ...


1

rarely? I see them all the time. Half the windows I have open right now contain tree views, and half the other half are either console windows or this web browser loaded with SE. Tree views can be very useful, depending on context. It's just that ever more people seem to think they're "outdated" and try to find twisted ways to do things differently for no ...


19

There are several problems with trees: A tree is a single taxonomy. This requires the user's mental model to match the software developer's mental model of the domain. Navigating with trees requires high-precision mouse accuracy to expand a tree without selecting the branch. This is also very difficult to manage with touch interfaces. Navigating trees ...


43

People don't generally use hierarchical structures 'in the real world' -- it seems to be something that has been forced upon them, a technical remnant of the past. What needs to be understood is the way that people recognise and organise things. Our brains don't work in a hierarchical way (without generating a lot of heat). Instead, we recognise things by ...


1

Big is good. Big is readable. If you give the user a sign of what they need to do it will be user friendly. Please use gestures, people like using gestures. Just make sure you add some sort of indication that will tell the user what to do and they should be able to use the feature.


3

I like the way Mint handles this kind of situation by automatically applying the UNCATEGORIZED category to the item. This term isn't as vague as Other and also explains to the user why the item is in that category. In mint's case the bold and all caps also draws attention to the item, which encourages the user to categorize the item.


1

I don't like using the word "others" because it seems to imply that the items do not have a category. If you are simply grouping categories into "others" for brevity, a potential solution is using "{n} other categories" or maybe just "other categories". I think this makes it clearer that the items do have a category, but they are grouped together just for ...



Top 50 recent answers are included