Difference between revisions of "Projects/Usability/HIG/Presentation/DesignVisionPrinciples"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
m (Purpose)
m
 
(20 intermediate revisions by one user not shown)
Line 1: Line 1:
 
__NOTOC__  
 
__NOTOC__  
== Purpose ==
+
=Design Vision and Principles=
Visual design is driven at the highest level by a design vision. Design principles are the principles we rely on to fulfill that design vision. These principles should guide all aspects of the visual design as a way to ensure that the design vision is being satisfied.
+
[[File:HIGDesignVisionFullBleed.png]]
 +
<div style="text-align: center;">''Simple by default, powerful when needed.''</div>
  
== Guidelines ==
 
=== Design Vision ===
 
[[File:VDGOverview.jpg]]
 
<div style="text-align: center;">''The future that never was; clean, technical, but human.''</div>
 
  
 +
Design is driven at the highest level by a vision. We rely on a set of design principles to fulfill that design vision. These principles guide all aspects of the user interface design.
  
The design vision is focused on two attributes that connect the KDE community's past to it's future.
+
== Design Vision ==
 +
The design vision is focused on two attributes of KDE software that connect its past to its future.
  
* ''Capable'' - Power and flexibility. KDE Applications and Workspaces allow users to be effortlessly creative and efficiently productive.
+
* ''Simple by default'' - Simple and inviting. KDE software is pleasant to experience and easy to use.
* ''Human'' - Simple and inviting. KDE Applications and Workspaces are pleasant to experience and easy to use.
+
* ''Powerful when needed'' - Power and flexibility. KDE software allows users to be effortlessly creative and efficiently productive.
  
=== Design Principles ===
+
== Design Principles ==
 
The following design principles are used in support of the Design Vision.
 
The following design principles are used in support of the Design Vision.
*Capable
+
*Simple by default
 +
** ''Make it easy to focus on what matters.'' - Remove or minimize elements not crucial to the primary task. Use spacing to keep things uncluttered. Use color to draw attention. Reveal additional information or optional functions when needed, not before.
 +
** ''I know how to do that!'' - Make things easier to learn by reusing design patterns from other applications.
 +
** ''Do the heavy lifting for me.'' - Make complex tasks simple. Make novices feel like experts.
 +
 
 +
*Powerful when needed
 
** ''Solve a problem.'' - Identify and make very clear to the user what need is addressed and how.
 
** ''Solve a problem.'' - Identify and make very clear to the user what need is addressed and how.
** ''Always in control.'' - The user should never feel at the mercy of the tool. It should always be clear what can happen, what is happening and what happened. Give the user the final say.
+
** ''Always in control.'' - It should always be clear what can be done, what is happening and what happened. The user should never feel at the mercy of the tool. Give the user the final say.
 
** ''Be flexible.'' - Provide sensible defaults but consider optional functionality or customizations that do not interfere with the primary task.
 
** ''Be flexible.'' - Provide sensible defaults but consider optional functionality or customizations that do not interfere with the primary task.
  
*Human
+
 
** ''Make it easy to focus on what matters.'' - Remove or minimize elements not crucial to the primary task. Use spacing to keep things uncluttered. Use color to draw attention.
+
{{Prevnext2|nextpage=Projects/Usability/HIG/Concept|nexttext=Concept|index=Projects/Usability/HIG#Getting_Started|indextext=Back to Getting Started}}
** ''Make important things fast.'' - Not all actions are equal. Make important information or functions easy to find and use.
+
 
** ''I know how to do that!'' - Make things easier to learn by reusing design patterns from other applications.
+
 
** ''Do the heavy lifting for me.'' - Make complex tasks simple. Make novices feel like experts.
+
<span style="font-size: 85%">Elements of these guidelines have been adapted, per license, from [https://developer.android.com/design/index.html Android Design].</span>
 +
 
  
 
[[Category:Usability]]
 
[[Category:Usability]]

Latest revision as of 17:31, 28 September 2014

[edit] Design Vision and Principles

HIGDesignVisionFullBleed.png

Simple by default, powerful when needed.


Design is driven at the highest level by a vision. We rely on a set of design principles to fulfill that design vision. These principles guide all aspects of the user interface design.

[edit] Design Vision

The design vision is focused on two attributes of KDE software that connect its past to its future.

  • Simple by default - Simple and inviting. KDE software is pleasant to experience and easy to use.
  • Powerful when needed - Power and flexibility. KDE software allows users to be effortlessly creative and efficiently productive.

[edit] Design Principles

The following design principles are used in support of the Design Vision.

  • Simple by default
    • Make it easy to focus on what matters. - Remove or minimize elements not crucial to the primary task. Use spacing to keep things uncluttered. Use color to draw attention. Reveal additional information or optional functions when needed, not before.
    • I know how to do that! - Make things easier to learn by reusing design patterns from other applications.
    • Do the heavy lifting for me. - Make complex tasks simple. Make novices feel like experts.
  • Powerful when needed
    • Solve a problem. - Identify and make very clear to the user what need is addressed and how.
    • Always in control. - It should always be clear what can be done, what is happening and what happened. The user should never feel at the mercy of the tool. Give the user the final say.
    • Be flexible. - Provide sensible defaults but consider optional functionality or customizations that do not interfere with the primary task.



Elements of these guidelines have been adapted, per license, from Android Design.


This page was last modified on 28 September 2014, at 17:31. This page has been accessed 3,146 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal