Complete the high priority background service implementations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
Critical
|
Pat McGowan | ||
Client Developer Experience |
Confirmed
|
Undecided
|
Unassigned | ||
ubuntu-application-lifecycle |
In Progress
|
Critical
|
Thomas Voß |
Bug Description
It frequently happens that people would want to implement applications but then give up again because their ideas can't be realized because of the current *very* limited implementation of the app lifecycle management. If one is listening around in the community, the sentence "I wanted to create that, but can't because of lifecycle" is part of the daily routine by now. Also I have heard several customers saying that they have flashed Android on their BQ devices because they couldn't be bothered any more to keep the display on to load a website, listen to some video's music, send a picture over telegram and much much more. Lately I explained to Pebble.com why RockWork (https:/
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
assignee: | nobody → Pat McGowan (pat-mcgowan) |
Changed in canonical-developer-experience: | |
status: | Confirmed → In Progress |
Changed in ubuntu-application-lifecycle: | |
assignee: | nobody → Thomas Voß (thomas-voss) |
importance: | Undecided → Critical |
status: | New → In Progress |
tags: | added: bq-feedback |
no longer affects: | canonical-developer-experience |
Changed in canonical-developer-experience: | |
status: | New → Invalid |
status: | Invalid → Confirmed |
We recently kicked off a discussion on priorities and work will be happening soon, and will loop in mzanetti and community