Apple’s Human Interface Design Principles features 13 topics:

• Metaphors
• Reflect the User’s Mental Model
• Explicit and Implied Actions
• Direct Manipulation
• User Control
• Feedback and Communication
• Consistency
• WYSIWYG (What You See Is What You Get)
• Forgiveness
• Perceived Stability
• Aesthetic Integrity
• Modelessness
• Managing Complexity in Your Software

Meanwhile, Microsoft’s Design Principles features only 5 topics:

• Top Guidelines Violations
• How to Design a Great User Experience
• Powerful and Simple
• Designing with Windows Presentation Foundation
• First Experience

The Apple principles are actual principals for user interaction while the Windows version seems more like hints and suggestions.

The document is written in such a way that someone without much technical experience would still be able understand it. Some of the guidelines I found most important were:

• Be prepared for the probability that users will not be giving their undivided attention to your content, at least not for long.
• Make sure your layout accommodates the average size of a fingertip and finding alternatives to drag-and-drop and cut, copy, and paste.
• Before you begin to work on your iPhone web application, be sure you know precisely who your users are.
• Minimize the number of controls from which users have to choose and labeling them clearly so users understand exactly what they do.
• A webpage that is cluttered with many different sizes and styles of elements, different sizes and colors of text, and gratuitous images presents an unpleasant user experience.
• When you ask for input from users, consider using lists (or pop-up menus) instead of text fields whenever possible.
• Make sure you use interactivity to get users closer to their goal and avoid interactivity that serves no functional purpose.
• Avoid technical jargon in the user interface.

10 to 3 to 1
Apple designers come up with 10 entirely different mock ups, designed without any restrictions of any new feature. They eventually decide on three and spend more months on them before finally ending up with one strong decision.

Paired Design Meetings
Two meetings each week. One to brainstorm and think freely of any restrictions. The sky’s the limit. And another production meeting which is the opposite and the engineers and designers try and work out all the details.

Pony Meeting
Everyone thinks they want a pony, but is that what the Users want (or need)? The best ideas from the paired design meetings are presented to leadership to transform the pony into requirements and deliverables everyone can agree upon.

—
Having done high fidelity mockups before, it really does take an enormous amount of time. However, it does give you results and removes a lot of questions and ambiguity. The 10 to 3 to 1 design process is great. I love the unfiltered creativity and Loop’s quote of the designs not being “seven in order to make three look good.” I’ve experienced it before. The paired design meetings are also a great idea. I remember having a creative no restrictions type of meeting before and the ideas that came out of it were spectacular (and even patentable). It is difficult for people to be creative when still thinking about the constraints. I read a good analogy for “The Pony.” A person may like ice cream and he may like pickles but that doesn’t mean he’ll like pickle-flavored ice cream.

All in all, it is nice to see that Apple takes the time to really think outside the box. Now if only other companies can be convinced to invest their time and money on the User Experience.