Jetpack/Roadmap/2013: Difference between revisions

Jump to navigation Jump to search
Line 56: Line 56:


== SDK API Development ==
== SDK API Development ==
=== P1 APIs ===


When we provide a new high-level api in the SDK, that api must provide a clear benefit to the add-on develop in terms of ease of use while still not impacting Firefox performance.
When we provide a new high-level api in the SDK, that api must provide a clear benefit to the add-on develop in terms of ease of use while still not impacting Firefox performance.
Line 63: Line 61:
# Places API. Bookmarks and history are probably the most interesting stores of data in Firefox and in particular the most interesting to users. Providing performant and usable apis to access this data easily could enable all manner of browser / user innovations.
# Places API. Bookmarks and history are probably the most interesting stores of data in Firefox and in particular the most interesting to users. Providing performant and usable apis to access this data easily could enable all manner of browser / user innovations.
# Awesomebar API. The awesomebar is *the* primary piece of browser UI, used more than anything else. As experiments like Bryan Clarke's [https://github.com/clarkbw/searchspot/tree/awesomebar searchspot add-on] have shown us, it can be very powerful to inject custom results into the awesomebar.
# Awesomebar API. The awesomebar is *the* primary piece of browser UI, used more than anything else. As experiments like Bryan Clarke's [https://github.com/clarkbw/searchspot/tree/awesomebar searchspot add-on] have shown us, it can be very powerful to inject custom results into the awesomebar.
=== P2 APIs ===
# Intercepting Network requests. Several popular developer tool add-ons rely on the low-level nsiContentPolicy interface to intercept requests and provide enhanced views of the requested content. It should be trivial for add-on developers to intercept and react to a specific class of network requests.
# HTML5 Support. As the web platform gets more powerful, add-on developers should also benefit from new HTML5 apis. Previously captured in the 2011 roadmap as '[https://wiki.mozilla.org/Features/Jetpack/Make_Add-on_SDK_Hug_the_Web_Harder hug the web harder]', we feel that providing a more web-like environment is the simplest way to provide add-on developers with access to powerful apis such as Websocket, IndexedDb and various device apis.


= Persistant Goals =
= Persistant Goals =
Confirmed users
1,100

edits

Navigation menu