Hi team. I've encountered a UX / UI bug when trying to initiate a Hello call. I have two cameras connected to my computer (built-in laptop cam and dedicated USB cam). I also have a dedicated over-the-ear headset with a mic that I use for Vidyo. When I initiate a Hello call, I cannot select the camera or microphone that I want to use. As a result, I have not been able to initiate a call when someone can hear me. When I am invited to a call, I get to choose which audio and video devices I want to use for the call. (screenshot attached of the drop down window). When I initiate a call, the little popup window that allows me to email or copy a link offers no no such window and I cannot choose my audio and video setup. (smaller screenshot attached) The result: Hello defaults to my built-in web cam and no one can hear me through my computer's internal mic. I have not been able to successfully initiate a call where I can be heard (some would say that means the software is doing a great job!!) If I paste the link into my browser, I get the full screen experience and can control my settings. But the little window that pops up in my browser doesn't tell me to click or paste the link in. It seems to suggest that I can just make a call from right there. Should we create language or add a link that allows you to open a fullscreen experience for Hello? Also, if I start a call, I get the little pop up in the bottom right corner. If I then paste the link into my browser to get the full screen experience where I can control my camera options, the other party to the call is told that there are already two people on the call.

This is the experience if you click the shared link for a Hello call. If you initiate a call and paste the link you get this screen and can choose your audio / video options. The problem is, if you follow those steps, the person you're trying to talk to may get a message that there are two people already in the call.

(In reply to Ben Niolet from comment #0) > When I initiate a Hello call, I cannot select the camera or microphone that > I want to use. As a result, I have not been able to initiate a call when > someone can hear me. Selecting a default device is bug 1023933/bug 1023934. I know Sevaan is reviewing the UX there before we implement it, so cc'ing him here. One workaround for the sound issue as you're on Mac (though I think this can be applied on other platforms), is to: - Go into the Mac System Preferences -> Sound -> Input. - Select the input device you want to use for the call - Start the call. That's obviously not ideal, but its a possible workaround atm. > When I am invited to a call, I get to choose which audio and video devices I > want to use for the call. (screenshot attached of the drop down window). This is because you're being treated as outside the privileged Hello code, and hence it needs prompting for permission. We opted for the no-prompt for the conversation window as that provides a better overall experience for a user (though obviously we need to implement the previously mentioned bugs or something like them). > If I paste the link into my browser, I get the full screen experience and > can control my settings. But the little window that pops up in my browser > doesn't tell me to click or paste the link in. It seems to suggest that I > can just make a call from right there. Should we create language or add a > link that allows you to open a fullscreen experience for Hello? You can already pop the screen out of the browser, there's a little arrow on the toolbar that points up to the right. We've also got bug 1000157 on being able to go direct to full screen. > Also, if I start a call, I get the little pop up in the bottom right corner. > If I then paste the link into my browser to get the full screen experience > where I can control my camera options, the other party to the call is told > that there are already two people on the call. We don't currently recognize that clicking a Hello conversation link within Firefox has anything to do with the user's use of Hello. Fixing that is contained within bug 1066019. Hence, I think we've got these concerns covered by other bugs, did I miss anything? Otherwise, I think we could close this as a duplicate of one of the bugs.

I think you covered it all, then. Sorry for the duplication.

Thanks for the confirmation Ben. No problem with the duplication - I'd rather have these issues raised so that we know the real issues people are hitting and that we don't miss any.