|Service vs. Service||I choose:||Why?||But…|
|Self-hosted WordPress vs. WordPress.com||Self-hosted WordPress||Branding & Plugins|
|Facebook vs. MySpace||Facebook is more organized|
|del.icio.us vs. diigo||diigo||Web high-lighting||My community is on del.icio.us|
|Twitter vs. Plurk||Plurk||Timeline GUI||My community is on Twitter|
|Digg vs. reddit vs. Mixx||Mixx||Less hostile toward content creators|
|Yahoo! Mail vs. Gmail vs. Hotmail||Yahoo! Mail||yahoo.com is easier to remember for my connections||I really want to use Gmail|
|Yahoo! Messenger vs. Windows Live Messenger vs. Gtalk||Windows Live Messenger||Twice the maximum number of friends one account can add compared to that of Y!M||yahoo.com is easier to remember for my connections|
Posts tagged: gui
What is Yahoo! Pipes?
Pipes is a new mashup from Yahoo! that provides a GUI for building applications that aggregate Web feeds, web pages, and other services, creating Web-based applications from various sources. At the end of the process, user can choose to publish those applications.
The site works by letting users “pipe” information from different sources and then set up rules for how that content should be modified.
Tai Tran on Yahoo! Pipes
How to use Yahoo! Pipes
There are a series of videos to look at.
Firstly, please see the basics of Yahoo! Pipes
Other videos in the series:
When designing screens for enterprise systems, I frequently face an issue. There are too many fields to present for a user to complete an action (i.e. manage an order transaction). In terms of cohesion, since these fields serve one purpose, they should be put in one screen. But again, too many!
Too many of them clustering in one screen makes it look like a mess with texts, numbers and boxes. Not nice at all!
New design trends pushes this even further
The new design standard introduces alternating colored grids, text boxes with strong borders. All of these increase to size of elements, thus will make the screen narrower.
So we face a dilemma: should we put all relating fields in one screen, or break an action into multiple screens?
Put all in one screen
Break the information into multiple screens?
What’s your Focus?
There are a couple of things you can do:
- Review GUI Design Guidelines
- Review a high level document (i.e. Vision) to determine what the system is for and what it should look like in general
- Create different prototypes and propose them to the customers
The most important factors
Some factors to look into when composing your own solutions:
Number of clicks
Because user’s interaction with system is done chiefly through mouse motions, number of clicks is considered one of the most important factor of GUI design.
Most of the cases, my experience is that with a little twist in design, number of clicks can be reduced from 3 to 2. Not so frequently it can be cut down dramatically. 1 click seems trivial. However, a user may perform that action a thousand times per day, thus makes it worth the effort.
Efforts users have to spend to learn how to use the system
If a screen has too many fields, it would be confusing for first-time users to know how to locate information.
If it takes quite some screens to accomplish a task, it would be confusing for first-time users.
In the long run, the first solution would prove to be better when user has memorized the location of information sections.