Status
- Stage: Planning
- Release target: ?
Team
- UX: Patryk Adamczyk (IRC: patryk)
- UX: Josh Carpenter (IRC: jcarpenter)
UX Requirements
Last updated: Mar 28, 2012 (Patryk Adamczyk)
Questions
- 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
Next Steps
- Complete technical survey
- Complete "current implementation" survey
- Complete prior art survey
- Define UX requirements