Applications

From Openmoko

(Difference between revisions)
Jump to: navigation, search
m (→‎Required)
Line 2: Line 2:
 
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.
 
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. Applications in '''bold''' are required for mass production and the first shippment of handsets.}}
+
{{note| Applications listed on this page are listing in order of priority and by phase. 1st phase is for January. 2nd phase is more long term...when we are ready for mass market appeal.}}
  
  
Line 17: Line 17:
  
 
==Finger-Based Applications ==
 
==Finger-Based Applications ==
−
scrolling region should be user defined (left or right side)
+
 
−
=== Required ===
+
=== 1st Phase ===
−
* '''[[Dialer]]'''
+
* [[Dialer]]
−
* '''[[Main Menu]]'''
+
* [[Main Menu]]
−
* '''[[Music Player]]'''
+
* [[Music Player]]
−
* '''[[History]]'''
+
* [[History]]
 +
 
 +
=== 2nd Phase ===
 
* [[Clocks]]
 
* [[Clocks]]
 
* [[GPS Navigation]]
 
* [[GPS Navigation]]
Line 29: Line 31:
 
* [[Unit Converter]]
 
* [[Unit Converter]]
 
* [[Game]]
 
* [[Game]]
−
 
−
=== For a Rainy Day ===
 
 
* [[Guitar Tuning]]
 
* [[Guitar Tuning]]
 
* [[Code Memo]]
 
* [[Code Memo]]
Line 58: Line 58:
 
* [[Web Browser]]
 
* [[Web Browser]]
 
* [[Reader]]
 
* [[Reader]]
−
 
−
=== For a Rainy Day ===
 
 
* [[System Info]]
 
* [[System Info]]
  

Revision as of 09:56, 18 November 2006

Contents

Overview

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. 1st phase is for January. 2nd phase is more long term...when we are ready for mass market appeal.



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.
NOTE: Innovation usually happens at the bottom. What we need to do is provide consistent ways to develop and deploy appliations.


Finger-Based Applications

1st Phase

2nd Phase

Stylus-Based Applications

1st Phase

2nd Phase

Panel Applications

Panel Applications are individual executables residing in the Top Panel. They're usually indicating a status and offer a pop-up menu. We are not yet sure whether there is enough screen real estate for this huge number of panel applications.

Required

For a Rainy Day

Retrieved from "http://openmoko.org/index.php?title=Applications&oldid=2744"
Personal tools

Overview

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. Applications in bold are required for mass production and the first shippment of handsets.



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.
NOTE: Innovation usually happens at the bottom. What we need to do is provide consistent ways to develop and deploy appliations.


Finger-Based Applications

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

Required

For a Rainy Day

Stylus-Based Applications

1st Phase

2nd Phase

For a Rainy Day

Panel Applications

Panel Applications are individual executables residing in the Top Panel. They're usually indicating a status and offer a pop-up menu. We are not yet sure whether there is enough screen real estate for this huge number of panel applications.

Required

For a Rainy Day