Applications

From Openmoko

Revision as of 08:22, 27 August 2006 by Sean (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Overview

(Talk more about finger / stylus split philosophy)

General Principles

  • All modifications are saved instantenously, there should never be a save command
  • Make sure users can't make interface operation errors, or that the effects are easily reversible, instead of just notifying them us the potential consequences of their actions.
  • When you open a document you should be returned to the place where you were working when you last closed or save it (this is our concepts of sessions).
  • Label buttons with adjectives, which describe the state of the object affected
  • Designers should seek an efficient monotonous solution to gain benefits, including ease of learning, simplicity of implementation, minimization of documentation, and lowered maintenance costs.
  • Whenever you find yourself specifying an error message, please stop; then redesign the interface so that the condition that generated the error message doesn't arise.
  • Is the user gets no utility from a process, there is no reason to tell them that it is happening.

Finger-Based Applications

scrolling region should be user defined (left or right side)

Required

If Time Permits

For a Rainy Day

Stylus-Based Applications

Required

If Time Permits

For a Rainy Day

Panel Applications

Personal tools

Overview

(Talk more about finger / stylus split philosophy)

General Principles

  • All modifications are saved instantenously, there should never be a save command
  • Make sure users can't make interface operation errors, or that the effects are easily reversible, instead of just notifying them us the potential consequences of their actions.
  • When you open a document you should be returned to the place where you were working when you last closed or save it (this is our concepts of sessions).
  • Label buttons with adjectives, which describe the state of the object affected
  • Designers should seek an efficient monotonous solution to gain benefits, including ease of learning, simplicity of implementation, minimization of documentation, and lowered maintenance costs.
  • Whenever you find yourself specifying an error message, please stop; then redesign the interface so that the condition that generated the error message doesn't arise.
  • Is the user gets no utility from a process, there is no reason to tell them that it is happening.

Finger-Based Applications

scrolling region should be user defined (left or right side)

Required

If Time Permits

For a Rainy Day

Stylus-Based Applications

Required

If Time Permits

For a Rainy Day

Panel Applications