Closed Bug 1035554 Opened 11 years ago Closed 7 years ago

[User Story] Restricting background mobile data usage on a per-app basis

Categories

(Firefox OS Graveyard :: Gaia::Cost Control, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: vtsatskin, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:SMRTDATA-2-2][NaBfT])

User Story

As a cost-conscious phone user, I want to be able to restrict specific apps
from using data in the background so that they don't consume my data without my knowledge.

Acceptance Criteria:
1. Applications with their background data usage restricted should not be able to use mobile data while the application is not in the foreground.
2. Applications which are set from restricted to not restricted should be able to use mobile data while the application is not in the foreground.
3. Per-app restricting of background data use should be device specific and not tied to a particular SIM.
4. The toggle to restrict background data use in the UI should match up to the actual state of the restriction.
5. UX interaction and visual design matches UX spec: https://people.mozilla.org/~vtsatskin/specs/SmartData/
No description provided.
Summary: [User Story] → [User Story] Restricting background mobile data usage on a per-app basis
User Story: (updated)
Blocks: 1089983
Keywords: feature
Whiteboard: [ucid:SMRTDATA-2-2]
Whiteboard: [ucid:SMRTDATA-2-2] → [ucid:SMRTDATA-2-2][NaBfT]
blocking-b2g: --- → 2.2?
blocking-b2g: 2.2? → backlog
feature-b2g: --- → 2.2?
feature-b2g: 2.2? → 2.2+
QA Contact: jlorenzo
Taking this to keep track of (and probably work on).
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
[Tracking Requested - why for this release]:
feature-b2g: 2.2+ → ---
tracking-b2g: --- → ?
Assignee: chrislord.net → nobody
Status: ASSIGNED → NEW
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.