As a FF browser user (signed-in or not), I can set the default microphone/speakerphone device that will be used for audio conversations so that I don't have to set it for each call. Based on the work in bug 1026782, this adds the microphone/speakerphone option.
Users may have multiple microphone/speakerphone devices on their desktop. This setting allows selecting the default microphone/speakerphone device which will be used when answering or placing calls (no gUM dialogue).
https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#settings building off of 1023933: user not logged on, so will need to store locally in prefs and view jiggering. create settings menu with at least one setting - covers different views. p=4 getmozpref exists setmozpref doesn't exist
Depends on: 1026782
User Story: (updated)
Whiteboard: p=1 → [p=1]
pushing the platform bug to get client really good at detecting external hardware - instead of these bugs. usually we want settings when hardware isn't detected well and experience is already worse. maire to update with platform bug number
Whiteboard: [p=1] → [p=1, gecko]
Target Milestone: mozilla34 → mozilla35
I opened Bug 1043740 and needinfo'd RT for the info on this problem.
backlog: Fx36? → Fx37?
Priority: P1 → --
can you update the "Settings Page" UX for this. it's an old UX and believe this is somehow tied to the gear. we're looking to do in 39 - so lower than screen sharing by a lot
backlog: Fx38+ → Fx39+
Priority: P1 → P2
Severity: normal → major
backlog: Fx39+ → Fx38+
Priority: P2 → P3
Just putting a link to the old Settings UX for my own reference: https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#settings
Just a note here that I am looking into added Hello settings to our in-content preferences. The reason being that we don't want little settings all over the place. If I was a user looking to edit my settings, I would look at my general preferences first.
backlog: Fx38+ → backlog+
Points: --- → 1
Whiteboard: [p=1, gecko] → [gecko]
Posted a design here: https://bugzilla.mozilla.org/attachment.cgi?id=8587040
I don't think this & bug 1023933 should be P4 - I think they should be P3 minimum. Whilst we have no stats on how many devices people have, I can say that it cripples my use of Hello as the defaults don't match my camera setup. Hence I don't actually dogfood it in real calls as much as I should do - I only really test the link-clicker. When we do Firefox opening links in the conversation window, this is actually going to get worse for me. I suspect there are other potential dogfooders in this situation as well.
Weighing in here. I wanted to +1 Mark's thoughts in comment 11. (I'm on the user engagement team and am on this bug because I filed a duplicate of this when Hello debuted.) This issue has essentially kept me from using Hello. I have a hard time connecting a call if I initiate it because I can't choose my video and audio setup. I use an external web cam and a headset for audio and video. Can't use any of them for a Hello call that I initiate. But I can use them if someone else initiates the call. So while I'm not sure how many people experience this headache, I can confirm that Mark isn't alone.
Thanks guys, that all makes sense. I'm marking as P3 and let's assess how much effort is involved here to help prioritize accordingly - to start that Sevaan can you please confirm that the UX you suggested on Comment 10 still applies? (what is applicable for this bug and bug 1023933 would be settings for Default camera and default microphone only).
Flags: needinfo?(rtestard) → needinfo?(sfranks)
Priority: P4 → P3
No, that attachement is obsolete. A more up-to-date one can be found in Bug 1023933 (https://bugzilla.mozilla.org/attachment.cgi?id=8588717&action=edit), but we may want to strip out the sound options since we don't have any at the moment (but let's include it in the roadmap somewhere so we don't forget) RT, you had some comments here: https://bugzilla.mozilla.org/show_bug.cgi?id=1023933#c23 Are those changes necessary at this stage? Let me know what to update and I can do it.
(In reply to Sevaan Franks [:sevaan] from comment #14) > No, that attachement is obsolete. A more up-to-date one can be found in Bug > 1023933 > (https://bugzilla.mozilla.org/attachment.cgi?id=8588717&action=edit), but we > may want to strip out the sound options since we don't have any at the > moment (but let's include it in the roadmap somewhere so we don't forget) > > RT, you had some comments here: > https://bugzilla.mozilla.org/show_bug.cgi?id=1023933#c23 Are those changes > necessary at this stage? Let me know what to update and I can do it. Thanks Sevaan, only comment I have is we should remove the "default answer mode (we'll rather implement an audio only option way to join in-product). Mark is this something that would rely on a separate team to be implemented or would the Hello team do this? It would be good to assess the size of effort in order to help prioritize this but I'm not sure who best could help us there?
(In reply to Romain Testard [:RT] from comment #15) > Mark is this something that would rely on a separate team to be implemented > or would the Hello team do this? It would be good to assess the size of > effort in order to help prioritize this but I'm not sure who best could help > us there? We can do this within the Hello team. We'd estimate 2 people about 2 iterations to do the work for it though there's a few unknowns at the moment.
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.