Features/Jetpack/Easy Page Mods
|Directly Responsible Individual||`|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
Writing page-mod contentScripts in Jetpack takes a lot more effort than writing a similar userscript in Greasemonkey or Scriptish.
The workflow for writing a Greasemonkey script is something like: 1. Write script. 2. Refresh page to test it. 3. Make changes to script. 4. Refresh page to pick up the changes and test it.
To do the same thing in the SDK with page-mods, it's more like this: 1. Write script. 2. Do cfx run. 3. Wait for Firefox to start up. 4. Go to the page you're testing the script on, test it. 5. Make changes to the script. 6. Go to #2.
It's even worse if you're going through the Add-on Builder website, as you have delays/hangs/timeouts while the add-ons get packed up server-side.
2. Users & use cases
Target audience is add-on developers who iteratively change their add-on's scripts to test changes. Allowing the developer to more quickly/easily test their changes to contentscripts will allow them to finish their job more quickly, saving them from the frustration of waiting for Firefox to start and install the add-on.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes
Changing to "On hold" to get it out of the Inbox.