User's Manual

www.openmoko.com
12
Although OpenMoko is designed for smartphones that use a stylus, it
would be foolish to expect people to only operate their handsets with
stylus. For this reason, some core phone-related applications will be
developed with finger (as opposed to stylus navigation) in mind.
NOTE: Applications listed on this page are listing in order of priority and
by phase. 0th phase is for the developers preview release in March, 1st
phase is for late March. 2nd phase is September... when we are ready for
mass market appeal.
2-1-1 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 of 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 concept 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.
If the user gets no utility from a process, there is no reason to tell them