By Alex Yakima
Never had a feeling that all I use is perfect, even after I started using Mac. Just think about it, if you are using a computer for 10 years, how many times did you open menus? Enough to start thinking that the entire conventional concept of plain menus is optimal. But is it indeed?
Typical scenario, you open context menu to save a picture for example and in order to go see "properties" you need to make a pretty long distance compared to "Open In A New Window".
It was 2 years ago when I started using Songza - musik search engine. The site was designed by very well known usability guru Aza Raskin (Mozilla). And what I liked first and most was pie menus.
In this case you have menu items same distance from your mouse pointer. In other words it makes you spend almost the same amount of time to reach every item.
There's very simple but useful principle in ergonomics known as Fitt's Law:
Time required to rapidly move to a target area is a function of the distance to and the size of the target.
The bigger distance and smaller size of the target - the bigger time needed, and vice versa, bigger objects placed closer require less time to navigate to.
This is exactly what makes pie menus so efficient because all objects are on the same relatively small distance from the center and targets are relatively big. There's also another point to pie menus, since distance is the same, the experienced user has only to remember the direction which is pretty easy and minimizes time required for turning user goal into actual movement.
From the implementation standpoint it is evidently more difficult to develop such a menu, but the problem is rather in the tradition itself. You almost never develop conventional (plain) context menus on your own these days - all you need to do is just specify your item list in a configuration file or so and attach action listeners to them. Although there started appearing solutions for pie menus too. RadialM, for example.
Speaking of notable examples of pie menus:
Maya:
Dozens of computer games. Actually sometimes it makes me wonder big amount of brilliant UI ideas that spawn in gaming industry.
Gaming example is great for other different reason - ergonomics issues become visible. If navigation takes too much time, you simply not gonna make the level. But now think about it for a second... it's not that obvious when you browsing web sites or editing word document or else... during 10 years of hard work you spend boatload of time just to navigate in plain menus...![]()
UI: Pie Menus
Friday, July 17, 2009 2:04 AM
Filed Under: ergonomics, UI, usability |5 comments
Subscribe to:
Post Comments (Atom)
5 comments:
This concept is really often used in many places, but what stops it from gaining more popularity is that it will only work if there are no more then 4 or 5 items in menu. Imagine a pie of 20 pieces - it would be actually much less usable, comparing to conventional menu, not only because it would be more difficult to hit the necessary item, but also much more difficult to spot the necessary item. I like the idea, introduced in Leopard, where you can plain-text-search for necessary item.
Agreed. Sure amount of items matters. On the other hand though it is rather generic "simplicity" issue because having too many items in context menu is never too good be it plain- or pie type of menu.
On the Leopard side... do you mean these "menu pointers" that open up menu items for you and place that slick little arrow next to it? If that's what you're talking about then, yeah I love it too. We actually used similar idea on one of our projects - FireFox toolbar that guides user thru complex web site flows with similar arrows + hints.
...And BTW if I had a possibility to configure the menu on the first image I would only leave few items for my own use:
Open Link In New Tab;
Save Link As...;
Copy Image;
Save Image As...;
Properties.
These are the ones I use relatively often. Quite enough for what I need. 11 items would go away! 11!
Hot-keys are extremely popular all because of absolute simplicity. I doubt a pie menus idea could ever beat them.
Not that idea is not great but it just doesn't really look worth spending time on developing that kind of thing.
I'd also leave "Open image in new tab", "Copy image location" and several others, but surely get rid of "bookmark this and that" items. It's true, that context menus should contain only the most often used stuff.
As for hotkeys, there is one giant issue with them - you have to memorize them. It's easy to use 10 items in context menu everyday, but memorizing 10 shortcuts for the same actions is more annoying. Surely, as you work with the same application a lot, you gradually memorize more and more shortcuts, but you cannot remember all of them, and if you suddenly forget one you haven't used recently, it should be in popup menu, cause if not, you are bound to desperately dig through the main app menu (or use clever Leopard search). Basically, shortcuts are helpful addition to menus, but they are not the main means of navigation in any case.
Post a Comment