App Persistence

Registered by Kieran Fleming on 2010-06-07

Using the GPS uses a lot of battery. When should we stay running, and when should we shut down?

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Should pressing back always accomplish the same thing as pressing home? I think so, as users are confused enough already.
- I don't think so. In my mind (and in most other apps) the back button exits the application, with the Home (or red in my case) keeps the application running. ~KenBW2

If navigating or recording a trace the program should spawn a service with the icon in the taskbar (a foreground service). This way the user can get back to their task easily after taking a call, email, etc. When tracing a route, the service stops when recording stops. When navigating, the service stops when the user pressed the Clear route/Stop Navigation button. This button replaces the 'Directions' button in the menu.

Should we spawn a service to monitor the GPS so the 'average speed' stat is maintained? I think this isn't important enough. Do we need a preference in case someone wants this behaviour?

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.