Features/FlightDeck/Client side app
|FlightDeck as a Client-side App|
|Release target||FlightDeck 1.0|
|Status note||In order to more fully serve FlightDeck's add-on development use-cases, the app should be transitioned to work as an open web app. This would include building XPIs on the client and enabling offline use.|
|Product manager||Daniel Buchner|
|Directly Responsible Individual||Sean McArthur|
|Lead engineer||Sean McArthur|
|QA lead||Stephen Donner|
|Product marketing lead||Dan Horner|
Stage 1: Definition
1. Feature overview
Enable saving data to the client machine that will be used in constructing Jetpack-based add-ons locally. In addition, use these features to enable the app to operate in offline mode.
2. Users & use cases
This feature will decrease build times and allow the developer to continue working when they don't have connectivity.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
- Sync, edit, and save packages to IndexedDB
- Rework the front-end code, with the help of the Add-on Builder extension, to sync add-ons/libraries to IndexedDB for editing on the user’s local machine.
- Compile add-on XPIs locally
- With the help of the Jetpack Runner, make it possible for compilation of XPIs to be performed locally on the user’s machine.
- Enable offline use of the app
- Detect and handle the user entering offline mode. Writing of data should save on the file system and sync to FlightDeck servers when a data connection is established.
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes
|Security||sec-review-needed||when ready sched w/ curtisk|