Closed Bug 1449252 Opened 7 years ago Closed 7 years ago

Pass device types that are syncing to Mozilla.org via UITour

Categories

(Firefox :: Sync, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: adavis, Unassigned)

Details

**Context** Currently, we have a web socket that tells Mozilla.org if the browser is syncing. This allows the Mozilla.org team to avoid asking users to login or register given they know that the user is already syncing. Instead, they often tell users to connect another device. This web socket is used on the /sync page, the /send-tabs page and now the /whatsnew page. Recently, we used this logic on the /whatsnew page. What became more apparently is that we now need to better support users who already have a mobile device setup with their Sync account. Some users expressed that they felt spammed given they already had a mobile device syncing. **Request** Setup a webchannel that can be made available to Mozilla.org team so that they can both know 1) how many devices are syncing AND 2) what type of devices they happen to be.
From eoger: >I’m not super used to the code, but I think we have that capability already: https://searchfox.org/mozilla-central/rev/49cc27555d5b7ed2eb06baf156693dd578daa06f/browser/components/uitour/UITour.jsm#1603-1608 > >Turns out mozilla.org doesn’t use webchannels but custom events (UITour specifically), took me a while to track that down Given mozilla.org uses UITour specifically, I will adjust this bug request.
Summary: Pass device types that are syncing to Mozilla.org via web socket → Pass device types that are syncing to Mozilla.org via UITour
Just to clarify, "I think we have that capability already" means Mozilla.org already receives these infos when they request the current "sync" state [0]. They are just not using it at the moment. [0] https://github.com/mozilla/bedrock/blob/d9ba2b7b439810ea8563c0e5020af88cf296aacc/docs/uitour.rst#getconfigurationtype-callback Should we close this?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.