Closed Bug 1089983 Opened 10 years ago Closed 7 years ago

[Meta] Connectivity Control Per Application

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::Cost Control
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: pdol, Unassigned)

References

Details

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

User Story

Connectivity Control per Application enables users to specify how each application on their device can connect (using the mobile network, WiFi or both).

See child bugs for user stories.

Real world examples for this feature:
- I have a game that serves ads and has online score boards.  I don't mind using the game while on WiFi, but using it on mobile data means I'm paying for the ads and score board functionality, even if the game itself works fine without data.  I want to be able to restrict the game to only connect over WiFi.

- I have a sports score app that wakes up in the background to update scores periodically.  I only care about sports scores when I want to check them, so I turn off background data for the app which doesn't affect me seeing the scores when I move the app into the foreground.  I'm now assured that the app isn't costing me money without me knowing it.
No description provided.
Depends on: 1089984
Depends on: 1089985
Keywords: meta
Whiteboard: [ucid:SMRTDATA-2] → [ucid:SMRTDATA-2][NaBfT]
Blocks: smart-data
Depends on: 1070944
No longer depends on: 1070944
User Story: (updated)
User Story: (updated)
feature-b2g: --- → 2.2+
QA Contact: jlorenzo
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
QA Whiteboard: [2.2-feature-qa+]
[Tracking Requested - why for this release]:
feature-b2g: 2.2+ → ---
tracking-b2g: --- → ?
QA Whiteboard: [2.2-feature-qa+]
Assignee: chrislord.net → nobody
Status: ASSIGNED → NEW
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.