canmove, Confirmed users
548
edits
Features/Jetpack/SDK Support for Firefox for Mobile Addons: Difference between revisions
Jump to navigation
Jump to search
Features/Jetpack/SDK Support for Firefox for Mobile Addons (view source)
Revision as of 08:35, 14 July 2011
, 14 July 2011no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=SDK Support for Firefox for Mobile Addons | |Feature name=SDK Support for Firefox for Mobile Addons | ||
|Feature stage= | |Feature stage=Definition | ||
|Feature status=In progress | |||
|Feature version=TBD | |Feature version=TBD | ||
|Feature health=OK | |Feature health=OK | ||
| Line 21: | Line 22: | ||
Ideally, addons built using the SDK's high-level APIs should work on both FFD and FFM by default without requiring addon developers to specifically target mobile devices, f.e. high-level APIs that enable addons to introduce chrome elements should adapt those elements to the FFM and FFD interfaces. | Ideally, addons built using the SDK's high-level APIs should work on both FFD and FFM by default without requiring addon developers to specifically target mobile devices, f.e. high-level APIs that enable addons to introduce chrome elements should adapt those elements to the FFM and FFD interfaces. | ||
|Feature users and use cases=The target audience is addon developers. The use case is simply that an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) will use the SDK to create and add-on with either Desktop or Mobile in mind, and that add-on works in either platform with no extra effort or thought from the developer. | |Feature users and use cases=The target audience is addon developers. The use case is simply that an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) will use the SDK to create and add-on with either Desktop or Mobile in mind, and that add-on works in either platform with no extra effort or thought from the developer. | ||
|Feature dependencies=The feature may depend on landing support for specific interface elements in the FFM interface. | |Feature dependencies=The feature may depend on landing support for specific interface elements in the FFM interface. | ||
While there are elements to having support for out-of-process addons that will be necessary in the long run. We have determined that having e10s support is not a blocker to getting minimal support for mobile addons working. | |||
|Feature requirements=The feature must load an addon built using the SDK in both FFD and FFM. It should make addons that use only the high-level APIs provided by the SDK work by default on both FFD and FFM, although it may require addons to provide browser-specific code if it is not possible to make all APIs "just work" in both browsers. | |Feature requirements=The feature must load an addon built using the SDK in both FFD and FFM. It should make addons that use only the high-level APIs provided by the SDK work by default on both FFD and FFM, although it may require addons to provide browser-specific code if it is not possible to make all APIs "just work" in both browsers. | ||