Closed Bug 1080889 Opened 10 years ago Closed 9 years ago

[meta] ensure LOOP displays in Marketplace only to FxOS devices with matching device capabilities

Categories

(Tracking Graveyard :: Marketplace, defect)

Product:
Tracking Graveyard
Component:
Marketplace
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cgalimidi, Assigned: Harald)

References

Details

(Whiteboard: [dependency: marketplace-partners])

User Story

I am a FxOS user and I would like to use LOOP on my FxOS device. LOOP will let me
- talk using my device microphone
- take advantage of audio/video/data channels on my device
- use the peer-peer video capability (ht64)

When I look for the app in Marketplace, I should easily find it so that I can download it and use it on my device successfully.


I am a FxOS user but my device does not have these capabilities. I do not want to be able to download or see apps in Marketplace that will not work on my particular device. When I browse the Marketplace catalog I should not see LOOP in Category pages or search results.
No description provided.
Blocks: Loopmov_1_1
Summary: [project] ensure "ThisNewApp" displays in Marketplace only to FxOS devices with matching device capabilities → [meta] ensure "ThisNewApp" displays in Marketplace only to FxOS devices with matching device capabilities
Summary: [meta] ensure "ThisNewApp" displays in Marketplace only to FxOS devices with matching device capabilities → [meta] ensure LOOP displays in Marketplace only to FxOS devices with matching device capabilities
User Story: (updated)
Please comment with a list of platform features that are 2.0+ specific that LOOP depends on for B2G. We need create a bug for them and check how to do the feature detection.
Flags: needinfo?(oteo)
Flags: needinfo?(dcoloma)
(In reply to Harald Kirschner :digitarald from comment #1) > Please comment with a list of platform features that are 2.0+ specific that > LOOP depends on for B2G. We need create a bug for them and check how to do > the feature detection. The list of features currently used are: "moz-attention" "audio-capture" "moz-audio-channel-ringer" "moz-audio-channel-telephony" "camera" "contacts" "mobileid" "push" "speaker-control" "moz-firefox-accounts" "systemXHR" "video-capture" "mobilenetwork"
Flags: needinfo?(dcoloma)
Those are permissions but at least a good indication of the APIs/hasFeature needed. It seems like we should be OK when we enable feature bucket for api.window.Navigator.getMobileIdAssertion. All other permissions are either pre-2.0 or have no feature detection (firefox-accounts?).
Flags: needinfo?(oteo)
Whiteboard: [dependency: marketplace-partners]
Depends on: 1080925
clouserw what else does marketplace need to know in order to match LOOP to devices?
Flags: needinfo?(clouserw)
We need to finish buchets. We also need to add some new buchets identified in this doc in yellow. https://docs.google.com/a/mozilla.com/spreadsheets/d/1taJJAwmQIYozXVsfyYTZJU14aqJlh7IkIkMGFCmsafc/edit#gid=0
Blocks: 1097323
No longer depends on: 983880
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Flags: needinfo?(wclouser)
Product: Tracking → Tracking Graveyard
You need to log in before you can comment on or make changes to this bug.