Hot answers tagged ordering
16
11 items is a difficult number of things to arrange in more than one line, but it's very easy around a circle.
How about something like the following which might still be inkeeping with your needs
I also decreased the size of the icons in relation to the labels in my version, but this is just a mock up anyway - you can obviously take the idea and adapt ...
12
I prefer comments to be in chronological order and threaded.
That way, when comments turn into conversations - and they often do, those are easy to follow. Any other order of comments makes it impossible, or at least very hard.
Newest on top means you have to go down to see what is being responded to. And if you decide to start at the bottom, you are ...
10
The idea behind tags is the same as the idea behind labels in GMail: the ability to assign multiple tags to a single post/mail/.../item.
The GMail labeling of e-mails was born specifically to counter the need in most e-mail clients to archive an e-mail in a single specific folder which ususally would be part of a hierarchy of folders. So what do you do with ...
9
Just tried to improve the concept taken from above designs.
I tried to group functionality that works together.
Data sources | Arcgis server | coordinate systems describe connections to external systems.
Queries and Maps (i guess the mostly used functions) have moved to right hand corner where users will find it more easy to locate.
Product logo is ...
9
1.
You could split it into logical sections, where you have first 3 colums with these:
"Datasources", "ArcGis servers"
"Users", "Roles"
"Tools", "Settings"
And then the rest on a single line below:
"Coordinate Systems", "Maps", "Queries", "Layouts", "Reports"
2.
Have the Esri logo at top left, and the Dekho logo at top right. This way, the symetry ...
8
Though the number of steps you defined looks fine to me, This is going to be really hard question to answer unless you show screenshots of the pages in question since there are single page checkouts as well which handle the information density well and guide the user well.
But to answer your question, there is no right or wrong number of checkout steps as ...
7
I create a thing.
After I create it, I preview it.
If I like what I previewed, then I publish it.
After I've published it, I want to share it.
Once I've shared it, I want to get stats on it.
When I'm all done with it, I delete it.
So - preview -> publish -> share -> stats -> delete - completely logical!
In addition delete makes good sense not to be in ...
7
Vertical lists are much easier to scan than horizontal lists, because all items are aligned to the same line, so when you're looking for an item, you don't need to read the entire word - you can quickly scan the first letters and get directly to the item you need. See how much less time it takes you to locate items beginning with P on Craigslist (within a ...
7
Is the equity of choice a good thing for the user? If the user could benefit from better load balancing due to shorter queue times, longer assistance or better resources, why not expose that fact to the users and let them choose less busy staff for their own sake?
If the equity isn't useful for the user, try exposing more points of difference in the list so ...
6
I personally feel like if you try to think of your application as a real life human being, then it helps design all the interactions with a user in a more meaningful way.
So in this example, the user wants to ask your app a question/enquiry. Now if your app was a human being, how would that play out?
User: Hello, I have a question. Do you have the Planet ...
5
To be a bit simplistic, the more orderly the layout seems, the more the order has meaning to users.
Masonry-style brick layouts, to varying degrees, subvert traditional orthographic order.
I would suggest that this subversion is intentional, and this subversion accounts for the charm of these interfaces. The layouts are unpredictable, and I am ...
5
It's a tradeoff. Chronological order is better for readability of threads, worse for diminishing the value of comments from latecomers, and for enabling early-bird campers to permanently stamp their agenda on the page.
This sums the first readability problem up neatly (credit: someone's forum signature, I forget where):
They break the natural flow of a ...
5
If you have nothing else to guide a sorting order, alphabetic makes the most sense. At the very least it creates an affordance for repeated use, where people will likely recall the name of a previously used menu item before learning the position, and if they're asked to select an item from that menu by documentation or another person, they'll be able to find ...
5
And if it has maximum of 30 items and all of them are visible why you just not place an action at the end of the list and add an ability to quickly reorder the list?
So, position of the new item will be obvious. And you can keep the selection untouched in this case.
4
I think ordering menu items is a bit less strict and more flexible than that.
First of all, the ordering is not perceived strictly top to bottom: there are actually three relative positions that people will use (and remember): top, middle and bottom. Rearranging items will mostly put off users when it is sorting with this relative order, but some individual ...
4
My first thought would be alphabetically, because this is static and generally easy to find what you want - assuming that you can show everything on one page, and scrolling is not needed to see others, particularly common ones. As long as your names are clear, this should be easy to learn and use.
Adaptive menus are a definately no no. Changing the orders ...
4
You could balance the workload by assigning points to the translators but hiding those from the user. Let's say we have 5 translators: Alfred, Bianca, Carlos, Dave, and Eliza. Assuming lazy users we'd expect Alfred to shoulder most of the workload, especially in a very long alphabetized list.
Instead, let's say that every time a translator completes a ...
4
There are two main eye patterns for web design.
The first: F-Shaped Reading Pattern
The second: ZigZag/Triangle Reading Pattern
Deisngs that fit into one of these two will work well with user. However if you are looking to get even more creative you can try out using the Golden Ratio to design a webpage, specifically placing content in the golden spiral ...
4
37signals has a great example of how you can make this interesting for the user and help them understand your story.
No offense to the HR professional who commented (though, it wouldn't be the first time I've offended HR), a history page that starts with the present is probably too much about what you want to say. Your current achievements are, hopefully, ...
4
You should present the most important information first, and so that will determine the order that you present the logs in.
For most logging applications, the most recent logs are more important, and so it's better UX to present the newest items first.
However, there are situations where each log is fairly long, and either the older logs are more critical, ...
4
Users typically want to see the most recent activity first. Think tweets, online banking transactions, news updates. It makes it easy to see what's new since you last checked.
With conversations, it's different because there is the context of whatever message came before and after the one you're looking at. It's a similar situation to what you see in ...
3
Sometimes (I guess more often than not) very good translations require some domain knowledge. How about listing the fields of expertise of each translator in addition to name and language? This might distribute the requests for assistance and at the same time increase the quality.
Regarding your options:
A click counter on the email address might not work ...
3
The best way to minimize bias in voting is to have random contestant ordering. Any ordering other than random will introduce a bias that favors what appears at the top, whether it's the ones already winning, those who come alphabetically first, or whatever other consistent sorting you choose.
To allow contestants to provide 'vote for me' links, you can use ...
3
We are facing a similar situation where our client has a huge catalog and wants to allow its users to successively filter down the content by drilling down into a hierarchy defined by them; a hierarchy they can decide to change anytime and as much as they want. Add to that the fact that the target platform is Android, its omnipresent back button and ...
3
Though I agree in part with the answers already posted, you can impose structure on tags. Rather than using 'hierarchy', a better term is 'relationship'. Consider some of the potential relationships between two tags:
is parent of
is child of
is type of
is subset of
is opposite of
Of course, each type of tag relationship adds extra complexity to your user ...
3
Your options for sorting things are as follows:
Frequency of use, with more frequent items at the top. This is often a good choice even when all items are visible at once. With a drop down, you know the mouse is initially at the drop down arrow, so this puts the most frequent choices closer to the mouse for faster selection, consistent with Fitts Law. This ...
3
I would go with option E - most people read from left to right. They examine things from the left and then slowly move to the right, if you have played games in the heydays of 8-bit you would see that most games have you start on the left and moving towards the right.
So it is easier to notice you could drag the items if the icon is on the left. However, I ...
3
It's already done (and proofed) by many others. Messages goes from newest to oldest and comments goes from oldest to newest. That's familiar, that's how e-mails (messages and replies), messages at facebook, etc are done.
You may use different views (chained messages, which will be organized into threads), or sorted by date (without any linking) like it's ...
3
As in many other things in life, this is an option that you can easily leave to the user. There are users who like a flat display order from newest to oldest, and there are users who like infinite threading. But as UX designers it is often our job to empower users with the options that they can chose from.
One of the best implementations on this thought ...
3
As an HR professional, reverse chronological is ALWAYS the preferred order when looking for information. I don't need (or want) irrelevant information.
I think you should determine how you want the information to be interpreted. Is it a story? From day 1. Is it a company update? Latest, first. You may need to evaluate who your audience is, as well.
The ...
Only top voted, non community-wiki answers of a minimum length are eligible
