So you do need somebody technical to make the space work how you need, and if your users are all non-technical you probably only want one type of rule everywhere or it'll confuse them.
If you do that, it works a treat.
1. You don’t see who is speaking when there are many people present— you have to scroll through participants to find the person talking. Lots of new employees, I didn’t know who was talking about half the time
2. Connection issues. I couldn’t hear the speaker but others could, for extended periods of time. Missed entire presentations due to this unfortunately, as I couldn’t hear or have any means of connecting to the speaker.
Don’t get me wrong it’s fun software, but it’s not ready to be your rock solid all-hands replacement quite yet. Had the pleasure of experiencing Welcome at one of the YC networking events, and that worked really well, curious to hear if they’re interested in filling this gap
Was the speaker at a podium? Were they spotlighted? Were you close to them?
There are several reasons why you might not have been able to connect that are part of the design. We found initially people were confused by the connection rules, but once they got the hang of it, it all "just worked".
I agree completely that it takes time to get used to, and perhaps you did have genuine connection issues, but we ran with 150 to 200 people for 48 hours without any significant[0] identified connection issues, which is why I wonder if it was mis-identification of a "symptom".
I'll check out "Welcome".
[0] There were occasions when people needed to reload the tab, but doing so always fixed the problem.
FWIW the person I could no longer hear was located across the globe, so maybe that’s related.
I apologize for not having a more thorough write up of what happened, but it was certainly a real issue.
As for the other issue, active speaker detection is on our near-term roadmap. It's become more pressing for us too, as our team has grown and no longer fits in one page :P
Thanks for the feedback!
I’ll keep the feedback method in mind for future usages!
Also, I get it, having started to work with the WebRTC stack myself. While the service is free to use I think I can stomach a few issues while it’s actively being worked on :)