canmove, Confirmed users
548
edits
Jetpack/Roadmap-2011: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 18: | Line 18: | ||
1) [[Features/Jetpack/Out-of-Process_Addons | ''Enable jetpack to always create add-ons that take advantage of the Electrolysis (e10s) to run in a separate process.'']] Running an add-on in a separate process is important for users and the add-on developer as it makes it much easier to determine if an add-on is affecting the browser's performance. In addition, there may be some security enhancement as its much harder to exploit a vulnerability if its being run in a separate process. For Jetpack, we want to ensure that our users never even have to think about e10s or how to use it for their add-ons to run in a separate process. | 1) [[Features/Jetpack/Out-of-Process_Addons | ''Enable jetpack to always create add-ons that take advantage of the Electrolysis (e10s) to run in a separate process.'']] Running an add-on in a separate process is important for users and the add-on developer as it makes it much easier to determine if an add-on is affecting the browser's performance. In addition, there may be some security enhancement as its much harder to exploit a vulnerability if its being run in a separate process. For Jetpack, we want to ensure that our users never even have to think about e10s or how to use it for their add-ons to run in a separate process. | ||
2) [[Features/Jetpack/ | 2) [[Features/Jetpack/SDK_Support_for_Firefox_for_Mobile_Addons | ''Support Firefox Mobile.'']] As we now all understand, the web experience is moving towards smaller devices, we have to make sure that any developer creating an add-on via Jetpack will find that their add-on just works in mobile. Mozilla cares as much about user choice and personalization on mobile devices as it does on the desktop, Jetpack must reflect that with no work from end-user developers. | ||
3) [[Features/Jetpack/Add-on_SDK_Localization_API_and_Service | ''Add-on Localization API and Service.'']] Its important that Jetpack no longer lingers behind in the the world-wide reach Mozilla has worked hard to obtain. We must have a localization solution that allows our developers to get localized add-ons with minimal effort on their part. Addon localization in the SDK comprises a simple, high-level API for specifying the strings to localize, a localization service to which addons distributed by AMO are automatically submitted for localization, a web application through which localizers can localize addons, and automatic repackaging of AMO-distributed addons with new and updated localizations. | |||
= Secondary Priorities = | = Secondary Priorities = | ||
1) [[Features/Jetpack/ | 1) [[Features/Jetpack/Traditional_Addon_Conversion_to_SDK_Platform | ''Create a path for developers using the traditional tools to move to jetpack.'']] If we are successful in bringing in new developers to creating add-ons for Firefox, we must not forget the developers who have been using the traditional toolset. With the inclusion of features such as e10s and mobile, it becomes imperative that we offer the easiest methods possible to create add-ons that work with these new technologies and platforms. We see Jetpack as being a great path for our current add-on developers to start taking advantage of these new features - as long as we can make the porting equally simple. This work includes creating tools which will automatically help developers port their existing add-ons, as well as a good set of documentation and examples to help them understand the differences in approach. | ||
2) [[Features/Jetpack/Simplify_the_Add-on_SDK | ''Simplify the Add-on SDK.'']] While Jetpack is a simple development tool to use as compared to the traditional add-ons tools Mozilla has offered, we have to recognize that simplicity opens the door for more participation. With more participation comes a greater democracy of ideas and implementations - all of which can benefit the open | 2) [[Features/Jetpack/Simplify_the_Add-on_SDK | ''Simplify the Add-on SDK.'']] While Jetpack is a simple development tool to use as compared to the traditional add-ons tools Mozilla has offered, we have to recognize that simplicity opens the door for more participation. With more participation comes a greater democracy of ideas and implementations - all of which can benefit the open web. Simplifying Jetpack even more is a high priority because it is one and the same with Mozilla's mission. The steps we can take to simplify Jetpack are: | ||
web. Simplifying Jetpack even more is a high priority because it is one and the same with Mozilla's mission. The steps we can take to simplify Jetpack are: | |||
* merge bootstrap.js and components/harness.js, dropping attempts at ff3.6/gecko1 compatibility | * merge bootstrap.js and components/harness.js, dropping attempts at ff3.6/gecko1 compatibility | ||