NewStory: Revise the UI to use the Android Design Patterns

[GoogleCodeExporter]

The first Alpha of the new DaisyReader app uses a single press to hear what the 
selection is and a long-press to select the item. These actions are not 
consistent with the majority of Android apps and our alpha testers found the UI 
hard to fathom until they were told what they needed to do. The app also worked 
reasonably well with explore-by-touch for the tester who is visually-impaired 
who prefers the 'visual mode' in terms of usability.

Therefore we would like to revise the user inputs to be more closely aligned 
with the Android guidelines. As the app is also aimed at users with Android 2.x 
and needs to work well for users who rely on audio feedback (the self-voicing 
aspect of the app) where Accessibility support is less developed for 2.x we may 
need to revise the UI design to balance these needs with those of working well 
for Android 4.x devices.

Original issue reported on code.google.com by julianharty on 19 Jun 2013 at 9:44

[GoogleCodeExporter]

I have posted comments in the story #65 
(https://code.google.com/p/android-daisy-epub-reader/issues/detail?id=65). 

Original comment by [email protected] on 25 Jun 2013 at 8:57

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by [email protected] on 24 Jul 2013 at 8:50

• Changed state: Started
• Added labels: ****
• Removed labels: ****