User Assistance. This is helping the user with the proper "next step" when performing a task. Less guesswork for the user on what to do next makes for a better experience.

This topic is one we will tackle later in this article, but it refers to making sure that your application and the dock aren't fighting it out for supremacy of the screen.

Adopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.

To put my money where my mouth is, in each new article I'll build a hypothetical application that illustrates the guidelines I'm covering. Today's application is called "Paint" and will be based on the photo-illustrative icon I created in my last article. Together we will complete each step, and by the end of the project we should have a well-designed, 95%-100% Aqua-compliant application. I'll leave some room for personal preferences and the fact that Apple changes the OS every few months.

Dock Animation. Sometimes animating icons in the dock can be useful in communicating the status of the system or application.

Okay, I just told you what Apple wants you to look out for with window positions, but in the real world, not everyone uses the hiding feature of the Dock, and it is unrealistic to be able to predict where each user will place their Dock at any given day or how large they will have it. However, you can build a feature into your application that allows spacing for the Finder. You can give users the option of where to position their windows and what area of the screen not to cross. I know that BBEdit provides me with this feature, and I wish more developers gave me more control over my windows.

You Must Promise. To call your mother, to help old ladies cross the road, and to turn your cell phone off at the movies.

Adhere to Window Models. Document windows, Utility windows, Click-through, Layering, Drawers, Controls. How do users open windows, how do you properly title windows?

User Assistance. This is helping the user with the proper "next step" when performing a task. Less guesswork for the user on what to do next makes for a better experience.

Thanks for signing in, . Now you can comment. (Click here should you choose to sign out.)

As you post your comment, please mind our simple comment policy: we welcome all perspectives, but require that comments be both civil and respectful. We also ask that you avoid the extensive use of profanity, racist terms (neither of which we consider civil or respectful), and other boorish language.

We reserve the right to delete any comment, and to prohibit you from commenting on this site, if we feel you have broached this policy. As a courtesy, we will first send you an email noting a violation so you understand the boundaries. This will occur only once, however, and should we ban you from our comment forums we expect that ban to be permanent.

We also will frown upon those who suggest that we ban other individuals for voicing unpopular opinions, should those opinions be voiced in a civil and respectful manner. The point of our comment threads is to provide a forum for spirited though civil and respectful discourse … it is not to provide a forum in which everyone will agree with your point of view.

If you can live by these rules, welcome aboard. If not, then we’re sorry it didn’t work out, and thanks for visiting The Command Post.

URL:
Remember me? YesNo

Comments: