canmove, Confirmed users
548
edits
Jetpack/Roadmap-2011: Difference between revisions
Jump to navigation
Jump to search
→Top Priorities
No edit summary |
|||
| Line 16: | Line 16: | ||
To that end, our top priorities for 2011/2012 are: | To that end, our top priorities for 2011/2012 are: | ||
1) [[Features/Jetpack/ | 1) [[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. | ||
2) [[Features/Jetpack/ | 2) [[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. | ||
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. | 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 = | ||