Improving user experience

From Openmoko

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
−
Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience.  Here
+
=Overview=
−
is our todo list, feel free to put your vote and add main issues that you think is critical.
+
  
−
as a proposal:
+
Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience.  The focus and coverage of this group is:
  
−
'''Priority:''' measured from 1 (highest) ... 5 (nice to have); put your priority into the comma separated list and we calculate later the average;
+
* We improve the current stack instead of creating new features.
 +
* Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific.
 +
* Won't work on om2007 stack.  Won't do hardware.
 +
* May cooperate with Paroli, FSO or system team but we're not them.
 +
* Will work on Qtopia but with lower priority.
  
−
'''Votes:''' just edit and add +1 if you wote YES|NO in the corresponding column;
+
=ToDO=
  
 +
Here is the current ''draft'' and it will be updated frequently.
  
−
{| border=1 cellspacing=0
+
* call quality
−
!Issue
+
** echo (in testing [http://docs.openmoko.org/trac/ticket/1267 #1267])
−
!Priority
+
** volume (alsa-state?)
−
!Yes votes
+
* Reduce boot time
−
!No votes
+
* Optimize the touch screen driver on freerunner for finger usage.
−
|-
+
* A generic python loader to enhance the start up time of python scripts.
−
| Reduce boot time ||5,3,1,3,3,2,3,4,3 ||4 ||
+
* qtopia
−
|-
+
** bugfix
−
| Optimize the touch screen driver on freerunner for finger usage ||5,2,1,3,1,4,2,7,2 ||5 ||
+
** program startup speed
−
|-
+
** response time
−
| A generic python loader to enhance the start up time of python scripts ||2,5,5,2,3,5,4,2 || 2 ||
+
* network
−
|-
+
** scripts: resolv.conf, etc.
−
| Work with system team to improve suspend/resume user experience ||2,1,1,1,1,5,2,1,1 ||6 ||
+
 
−
|-
+
==Evaluating==
−
| We improve the current stack, not creating new features ||1,4,1,2,1 ||4 ||1
+
 
−
|-
+
* suspend/resume
−
| Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific ||5,5,4,5,4 || ||5
+
** take a screenshot before suspend. display it on screen first thing on resume.
−
|-
+
** do not suspend when usb connected, qtopia indexing, etc.
−
| won't work on om2007 stack ||5 ||3 ||
+
* qtopia
−
|-
+
** change the button order of "end call" or "ans call"
−
| working on improving the Xglamo ||4,1,3,3,3,3,2 ||6 ||
+
** put speaker button on the dialer app
−
|-
+
* peripherals
−
| afair 3d and video (ie playing videos) still need work ||5,3,3,2,4,2,5 ||3 ||
+
** LED & button behavior [[FreeRunner/Buttons and LEDs]], [[FreeRunner LED signals]]
−
|-
+
***illume: disable suspend by power button when screen blanked
−
| Program response should be lots better. Startup time reducing for apps would be great ||5,1,2,3,1,2,2 ||5 ||
+
* devices (command line improvement first)
−
|-
+
** GPRS
−
| Suspend is quite good at the moment, but when the display is 'blanked' and the system is not in suspend, maybe pressing the 'power' button could wake up the screen instead. Now it wakes up and immediately suspends ||5,5,1,4,3||3 ||
+
** bluetooth
−
|-
+
** wifi userspace
−
| my suspend / resum still kills my sound ||2,2,2 ||3 ||
+
* misc
−
|-
+
** opkg: faster algorithm
−
| The "suspend on power button" is completely useless for me ||1 ||1 ||2
+
 
−
|-
+
[[Category:Community]]
−
| touch and accellerometer based gui for nearly blind people ||2,5,3 ||1 ||
+
−
|-
+
−
| make a dialer compatible with bbdb ||5 || 1||
+
−
|-
+
−
| make a gnus backend for sms ||3 ||1 ||
+
−
|-
+
−
| a symbol chooser keyboard ||3,3 ||2 ||
+
−
|-
+
−
| Keyboard improvement ||1,1,1,1,1,2,6,4 ||6||
+
−
|-
+
−
| Solve the call quality problems (echo, buzzing, volume) for 99% of the users ||1,1,1,1,1,1,1,1,1,1,1,2 || 12 ||
+
−
|-
+
−
|Solve the illume resume problems. They have been talked about over and over, but infortunately the information is scattered and imprecise. the tickets themselves have misleading info (I should know,I helped confuse you...), so maybe this deserves a new single ticket,where everyone contributes with more exact information; ||3,1 ||2 ||
+
−
|-
+
−
| Get the wifi driver corrected ||1,2,1,1,1,2,1,1,4,2 ||7 ||
+
−
|-
+
−
| Integrate FSO framework in OM2008  ||2,2,2,3 ||4 ||
+
−
|-
+
−
| Make the Freerunner work as a reliable phone, for voice calls and SMS, with decent battery life (at least 24 hours) || 1|| 1 ||
+
−
|}
+
  
 
[[Category:Community]]
 
[[Category:Community]]
 
[[Category:Community]]
 
[[Category:Community]]

Revision as of 19:55, 17 October 2008

Overview

Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience. The focus and coverage of this group is:

  • We improve the current stack instead of creating new features.
  • Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific.
  • Won't work on om2007 stack. Won't do hardware.
  • May cooperate with Paroli, FSO or system team but we're not them.
  • Will work on Qtopia but with lower priority.

ToDO

Here is the current draft and it will be updated frequently.

  • call quality
    • echo (in testing #1267)
    • volume (alsa-state?)
  • Reduce boot time
  • Optimize the touch screen driver on freerunner for finger usage.
  • A generic python loader to enhance the start up time of python scripts.
  • qtopia
    • bugfix
    • program startup speed
    • response time
  • network
    • scripts: resolv.conf, etc.

Evaluating

  • suspend/resume
    • take a screenshot before suspend. display it on screen first thing on resume.
    • do not suspend when usb connected, qtopia indexing, etc.
  • qtopia
    • change the button order of "end call" or "ans call"
    • put speaker button on the dialer app
  • peripherals
  • devices (command line improvement first)
    • GPRS
    • bluetooth
    • wifi userspace
  • misc
    • opkg: faster algorithm
Retrieved from "http://openmoko.org/index.php?title=Improving_user_experience&oldid=57420"
Personal tools

Overview

Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience. The focus and coverage of this group is:

  • We improve the current stack instead of creating new features.
  • Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific.
  • Won't work on om2007 stack. Won't do hardware.
  • May cooperate with Paroli, FSO or system team but we're not them.
  • Will work on Qtopia but with lower priority.

ToDO

Here is the current draft and it will be updated frequently.

  • call quality
    • echo (in testing #1267)
    • volume (alsa-state?)
  • Reduce boot time
  • Optimize the touch screen driver on freerunner for finger usage.
  • A generic python loader to enhance the start up time of python scripts.
  • qtopia
    • bugfix
    • program startup speed
    • response time
  • network
    • scripts: resolv.conf, etc.

Evaluating

  • suspend/resume
    • take a screenshot before suspend. display it on screen first thing on resume.
    • do not suspend when usb connected, qtopia indexing, etc.
  • qtopia
    • change the button order of "end call" or "ans call"
    • put speaker button on the dialer app
  • peripherals
  • devices (command line improvement first)
    • GPRS
    • bluetooth
    • wifi userspace
  • misc
    • opkg: faster algorithm