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 16:22, 4 August 2011
, 4 August 2011no edit summary
mNo edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
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. In addition, if the developer wants their add-on to only work on FFM or FFD they should have the ability to toggle a flag to make it singular to that platform. | ||
|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. | ||
| Line 47: | Line 47: | ||
Design and implement additional API features for capabilities that are specific to mobile devices. | Design and implement additional API features for capabilities that are specific to mobile devices. | ||
|Feature ux design='''Phase One''' | |||
Coordinate with the UX team and Jetpack developers to map out the interface elements that are exposed in the APIs to FFM. This stage is critical in making add-ons usable and worth the effort. | |||
'''Phase Two''' | |||
Implement the mappings. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||