100 ways to "Save As..." a cat

It recently hit me how no two of my coworkers save their files in Flex Builder the same way. One uses Save under File, another always uses Save All, yet another hits the save disk icon. And I use the keyboard shortcut or let Flex Builder save everything for me when I run the app. There are so many different ways to save your progress, how odd that no two people seem to do it the same way.

But it got me thinking, how many different options do you need to perform the same task? And what tasks need to have multiple entry points? How do you determine which tasks those will be?

As web application developers, we're in a odd position. People are used to how client applications work. There are drop down menus along the top, you can close the whole thing by clicking an icon in the upper corner. But just because our apps run inside a browser, doesn't mean we get to reinvent how applications look and work. People know how Word works, and if your app is totally different, they won't bother to learn it unless forced, and then they'll be frustrated. If your app is fundamentally different than the apps your users are used to, you need to have zero learning curve. I'm frustrated enough between home and work, switching between Mac and Windows. The Mac's apple button is about the equivalent of Windows' control key, but is where the Windows' keyboard's alt key is. It's annoying when something isn't where you're used to it being. Keyboard configurations or application design.

... What was my point ...

Repetition of commands...

If possible, watch a user using your application. Note where they first look or move the mouse. If your buttons are at the bottom and they go to the top, might want to move your buttons. Or duplicate the button on the top. Double-click the datagrid to open the editing form, or single click and hit the "Edit" button, or do something with right-clicks. The more ways you have of doing a single activity, the more maintenance for you, but the less of a learning curve for your users. The users will be able to "play with" your app and accomplish what they want because they won't have to think like you were when you designed it.