Jetpack/Roadmap/2013: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 16: Line 16:
== The State of Jetpack ==
== The State of Jetpack ==


If you look at the 2012 roadmap, there are a number of hits and misses, and some of the misses are copied into this document because we believe they are still valid ideas for the product. The main hits are:
By any measure, 2012 was a great year for Jetpack. We saw increasing adoption of Jetpack with 1000+ add-ons on AMO and climbing, and several SDK-based add-ons gathering thousands and in one case millions of users. We also saw major partners such as Yahoo, Springpad and 1Password ship SDK-based add-ons successfully. We grew the team and the contributor base somewhat, and we also delivered on all of our releases on time.  


If you look at the 2012 roadmap, there are a number of hits and misses, and some of the misses are copied forward into the 2013 Roadmap because we believe they are still valid ideas for the product. It is also worth looking at the hits, as some of the 2012 achievments directly inform our direction in 2013.
=== Needed Enhancements ===
* localization support
* mobile support is nearly complete
* mobile support is nearly complete
* simple-prefs landed
* simple-prefs
* major enhancements to page-mod
* major enhancements to page-mod
* vastly improved memory usage and greatly reduced performance issues
 
* broader adoption of Jetpack ( 1000+ add-ons on AMO and climbing )
=== Re-architecture ===
 
* re-organization of the SDK tree to better fit with the Firefox dodebase
* the CommonJS loader and Promise module shipped with Firefox 16
* numerous improvements and additions to the low-level implementation of the SDK in particular to improve the extensibility of the SDK's apis.
 
=== Stabilization ===
 
* we worked closely with the Memshrink project to * significantly improve memory usage and performance issues.
* we responded quickly to bugs in release versions with point releases
 
 
 
 
* SDK re-architecture  
* SDK re-architecture  


== The Roadmap ==
== The Roadmap ==


=== Re-architecture ===
 
=== Stabilization ===
=== Division of assets ===


In 2012 we worked hard towards two notable goals: cfx in JS & landing the SDK apis in Firefox. Now that these goals are a reality,  
In 2012 we worked hard towards two notable goals: cfx in JS & landing the SDK apis in Firefox. Now that these goals are a reality,  
Confirmed users
1,100

edits

Navigation menu