Revision as of 15:55, 28 March 2012

Status

Last updated: Mar 28, 2012 (Patryk Adamczyk)

Critical System Updates: Over the Air (OTA)
- Push Notification (status bar)
- Downloads and installs in the background, when prompted by the user
App Updates: Over the Air (OTA)
- Push Notification (status bar)
- Downloads and installs in the background, when prompted by the user

How much of implementation is B2G? How much Gaia? What technologies are involved?
What are our dependencies on externals, eg: Apps team?
How much control do we provide and/or require of the user? Transparent, or in-your-face?
Do we defined update "Types", eg: Kernel/Drivers, vs. Gecko, vs. Gaia.
Where is B2G / Gaia line? Will Apps run on any B2G implementation? If not, where is break point?
BusReq: Do we build in ability to carrier to push updates without user approval?
How do we create solution that satisfies our values, customer (Carrier) needs, end-user needs, security, and technology?
Legal implications: what are they? What are liabilities?
Do we help manage update risks? eg: Backup to local storage in case of update error.
Edge cases: eg: how do we manage user powering down device during long update?
Bandwidth: do we manage impact on billing by requiring updates go through WiFi? Or specific APN? etc.
How are updates pushed to user? Both from technical and UX standpoint

@@ Line 10: / Line 10: @@
 = UX Requirements =
 ''Last updated: Mar 28, 2012 (Patryk Adamczyk)''
+==Requirements==
+* Avoid System Restarts!!!
+* Download all updates at the same time (this should be a by default ON option)
+* Specify download limit for network, wifi is unlimited
+* Critical System Updates: Over the Air (OTA)
+** Push Notification (status bar)
+** Downloads and installs in the background, when prompted by the user
+* App Updates: Over the Air (OTA)
+** Push Notification (status bar)
+** Downloads and installs in the background, when prompted by the user
 ==Questions==