OS user interface guidelines: when to ignore? -


In a line, " Get used to using Mac on your own words "I have had a little disturbance, and started thinking about some of the things I had thought long ago and still have not come up with a good answer.

Each OS has its own guidelines on how the interface of an application is developed, it fits with the OS, and as a result the user's mindset

Anyone really applies any great degree (from different "programs made for xyz OS programs"), so it bothers me that I suggest functionality that is different from OS suggestions It is possible to make an option during the development of an application. It may be that the application is better with a different user interface, or it may be due to implementation, such as the webpage or cross-platform.

App Versus OS:

  • If I choose to develop against those UI recommendations, then what is a good reason for me to do?
  • Webapp vs OS:

    • If I'm developing a webapp, which means that it's a desktop app What I have to do is:
      • Develop and follow your own
      • Check the user's OS and follow that convention (and thus user
      • Cross platform versus OS:

      Follow the conference of another major webpamp (Gmail / Docs, Live, etc.)

      • To develop a cross platform
        • An OS
        • Use the Cross Platform Libraries
        • The custom interface for each OS which is completely original
      • / ul>

        I think it relies heavily on available resources, and other other unknowns, but this option is What are the ideas, strategies and logic you can use when you are considering

Even when a guideline is arbitrary, even then for any deviation the costs associated with external inconsistencies still occur, the cost can be difficult to measure, but it will be accounted for Designer's decision is an attempt to know the errors associated with external inconsistent costs, primarily deviation and trying to use deviation in the context of other apps. The effective cost for learning is low if Has been providing training and / or frequency of use is high (the latter due to the learning overhead). The frequency of errors for deviation is associated with frequency and context of application usage. The effective cost of errors is low if your app is used extensively and separately from other applications of the platform as a rule of thumb, as long as users do not use your app every day for hours You need to display the best user performance to keep the deviation right.

Generally, there is a more serious problem than the inconsistency in the UI behavior UI presence . Also, contradiction (Something that resembles something from the style guide but its meaning is something different) is more serious than the irregularities (something that looks different from some in the style guide but that means the same thing) .

Conformance with the OS style guide is more important to the app rather than conform to web conventions because web conferences are functionally weak, less applications are likely to come to the user to apply. Nobody should follow the conventions of any app like Gmail, at the cost of the OS guidelines, unless your users use a single app and an app is used in conjunction with your app. For maximum applicability, you should follow the guidelines of what your users are using. there is no substitute.


Comments