The other day, I came across the Apple Human Interface Guidelines, which is a document that helps guide developers to create consistent, easy to use applications that will run on Apple’s devices.

The guidelines are very detailed. Check the link above to see for yourself, or download the 28+ MB PDF version. While skimming the document, I ran into two interesting sections.

The first is titled “Involving Users in the Design Process, which states:

The best way to make sure your product meets the needs of your target audience is to expose your designs to the scrutiny of your users. Doing this during every phase of the design process can help reveal which features of your product work well and which need improvement.

When you give people an opportunity to use your product (or a prototype of it) you may uncover usability problems that you did not anticipate during your initial design phase. Finding and eliminating these problems early can save you time and money later on. Clearly identifying the needs of your users helps you create products that deliver effective solutions and are typically easier for them to learn and use. These improvements can translate into competitive advantages, increased sales, and enhanced customer satisfaction.

The second is titled “Keep Your Users in Mind“, and starts off with the following words:

In addition to the basic principles of interface design, consider the needs of your audience. Are your users more comfortable in a language other than English? Do they have special needs that might affect the way you present data to them? The following sections identify areas that might influence your design.

Admittedly, I don’t own a Mac. And I’m definitely not an Apple fanboy. That said, I’ve used and played with them sporadically over the years, though. Something that always struck me was the general consistency of the applications, and the (relative) ease of use of Mac OS. Obviously, there’s something to be learned from reading the Apple Human Interface Guidelines.

  • Share/Bookmark

Related posts:

  1. Apple’s audio documentation
  2. Document design: a visual overview
  3. What makes a good mobile interface?