Marketplace needs to be able to identify the capabilities of a device in order to present the consumer with apps filtered for their device, according to the use cases in the document linked below...


Scope of getFeature
- https://wiki.mozilla.org/WebAPI/Navigator.hasFeature 

Use Cases for Feature Detection:
- https://docs.google.com/a/mozilla.com/spreadsheets/d/1taJJAwmQIYozXVsfyYTZJU14aqJlh7IkIkMGFCmsafc/edit#gid=0


LOOP
- mobileid (*2.0 & getFeature)
- moz-attention (will get unprefixed in 2.1)
- moz-audio-channel-ring (will get unprefixed in 2.1)
- moz-audio-channel-telephony (will get unprefixed in 2.1)
- moz-firefox-accounts

WMW
- needs asm.js manifest precompile (1.4, 2.0 & getFeature)
- at least 512MB device (getFeature(hardware.memory) 2.0 & getFeature)
- 80 mb storage space available (install needs to fail if no space available)
- moz-firefox-accounts


Scope:
- need to land a new packaged app for marketplace in order to have the privilege / permission
- need to add the permission / api to the marketplace app itself
- new UI - disable feature detection if user is requesting to see all apps even those not compatible with device

User Flow
- app dev submits app, marketplace prechecks for the manifest fields. developer can add checks or uncheck.
- add mobileid check box during app submission flow
- consumer: app with the getFeature api will be rejected from marketplace
- consumer: i should not see apps that are not enabled for my version of fxOS (i am not on 2.0 or better and / or i do not have getFeature)


Out of Scope:
- marketplace package in 2.0 are not using feature permission
- cannot use getFeature on Android or Desktop (FxOS, Desktop)
- all apps will not have access to getFeature - apps within marketplace will not be able to detect device capability. the api is not exposed within marketplace. and app will be rejected from the submission flow
- user will need to upgrade marketplace app in 2.0 from iframe to


Technical Plan:
https://etherpad.mozilla.org/finishing-buchets