hi, Am Dienstag, den 18.08.2015, 07:51 -0400 schrieb Thomas A. Moulton: > It is very tricky and what makes it hardest is the app behavior depends > on the skill of the development team (or person) to write an app that > manages the phone's resources properly. > > I wonder if we are mixing short term and long term goals. > Many app, like games, utilities, etc do not have need to do much while > not the foreground task (active and facing the user) > > But there are going to be app of various kinds that rely on networking > and need to keep sockets open to other systems for long periods. > for such apps the plan is to have backend services that can constantly run. the UI part of your app should always be stopped (and even be able to be killed to free up resources for the fg app) when not focused while a non UI system service should still provide the needed functionality ... that way you cover the long running part while still allowing proper lifecycle management. we are just not completely there yet :)
the media-hub is a good example currently ... if an app uses it the UI
gets stopped (and if needed killed) if you unfocus it while your music
plays on ... over time more of such services are planned.
independently of the app lifecycle these services will/are also hooking
into the trust store, which is our system to allow access to hardware
and protection worthy system resources.
note that you can always sideload click packages (or soon snap packages
once teh phone switched over) that completely work around this, run
constantly and have full access to hardware and to stealing your
adressbook etc. all of the above only applies to packages uploaded to
the official store.
ciao
oli
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
