Comments (25)
I think simply making "camera / audio off" be the default when entering a room would be a big improvement -- maybe all we need.
from clowdr-web-app.
On a separate note: with a more stable video layout, entering a room with video/audio enabled would be much less disruptive as the videos wouldn't resize/move around/disappear.
from clowdr-web-app.
Perhaps my bias is that I already equate "vid/mic off" with "just listening or AFK" - anyone used to remote working or online gaming is likely to already have this association (based on my experience and the experiences of my long-time remote working friends at other companies). Perhaps we just need to tell people this in a notice on screen, for those who are new to remote work / conferencing?
from clowdr-web-app.
We're out of time for ICFP, but I still want to try experimenting with this.
from clowdr-web-app.
+1
Entering a room (with the camera on) can be quite disruptive to the people there. Audio only when entering to listen to the conversation and turning on your camera to participate may be a good balance.
from clowdr-web-app.
FYI for ICSE we started muted by default in big group rooms and people hated it. If we do camera/audio off by default, we need to make it extremely obvious (much more so than how it is now) that this is the case and how to do it. It would also probably be good to make the video/audio mute sticky across calls (so if you turn video off in one room then jump into another, still off, if it's on in one then jump to another, still on). It's our oldest open bug :) #3
b103489#diff-6f9cdfcc341448d4bf500001325d6e43
from clowdr-web-app.
Sticky video/audio seems like the most effective solution to me. Perhaps with having two options for joining a room: per-previous (ordinary join) or silent (muted join).
from clowdr-web-app.
from clowdr-web-app.
I think that's a terrible over-complication - if people are one click away from joining the room properly using the "move from just listening to participation button", that's the same as the video/audio enable/disable buttons.
I also think that labeling people in a separate section as "just listening" will have a significant negative impact: once someone is labeled as "just listening", it will raise the fear-level even higher of moving to contributing. In effect, by putting the label on screen for everyone to see (including the "famous people"), you increase the problem rather than decreasing it. This seems like a classic case of trying to use technology to solve a human problem: if people are afraid of joining rooms with "famous people" then that's a community problem (one which ICFP didn't seem to have, at least in my experience).
Also, at this stage, creating such a separate mechanism is going to be complex and costly compared to just having a button say "join muted" (which I think achieves the same result but without the stigmatizing label).
from clowdr-web-app.
(The alternative is some kind of invisible observation mode - which is diabolical because then participants in the room can't tell who's listening. People naturally become very closed and guarded if they think literally anyone could be listening and they don't know who.)
from clowdr-web-app.
from clowdr-web-app.
from clowdr-web-app.
On a separate note: with a more stable video layout, entering a room with video/audio enabled would be much less disruptive as the videos wouldn't resize/move around/disappear.
I think that this will solve a lot of our video chat usability problems. When you join a room, if you are video+audio on, you should show up either in the grid of people who have video on, or in a list (perhaps above that grid) that lets you select that person and see their video. If you have only audio on, or are fully muted, we should show you listed in some way to make extremely clear visually that you can not be clicked on to see your video (aka that you are "just listening).
from clowdr-web-app.
from clowdr-web-app.
I think we should follow Zoom's example: Layout everyone in a grid, try our best to always keep the positioning the same (boxes for participants are all equal size), and if someone turns off video, show their name in the box and if they mute, just add a muted symbol to their box. It's simple, effective, doesn't require lots of extra work, doesn't add unnecessary labels and will match user's experience on most other platforms (Zoom, MS Teams, Discord, etc) which will make it much easier for people to use our platform (there is no substitute for instant familiarity).
[Note: Account for 'presenter mode' separately]
from clowdr-web-app.
@EdNutting the one issue is that we can't show more than 4 videos at a time (even zoom can't in their web app, only in native) - I think that having everyone in the grid sets people up to expect zoom's native experience (up to 40 or however many video streams), which then is immediately disappointing.
from clowdr-web-app.
from clowdr-web-app.
@jon-bell The above conversation does nothing to address that particular problem... none of the alternatives to a grid layout solve the issue of not showing more than 4 videos at once. The grid layout makes solving that one a lot easier if a stable layout is desired (which I think it absolutely should be): you simply disable the video and replace it with their name (or continue to try the freeze-frame thing but with something other than greying-out which makes people think of disconnection).
@bcpierce00 There is a tradeoff between stability of the layout and making sure the right person is always on screen. In practice, dropping to a 3x3 grid and a maximum room size of 9 would be perfectly acceptable even on small mobile devices (with at most 4 video feeds on at once).
from clowdr-web-app.
(Or a 2x4 grid and a room size of 8 - depends a bit on which set of mobile devices you want to target - you can't win them all. Only fairly high end devices from the last 4 years are going to cope with a video calling app like this anyway)
from clowdr-web-app.
Would it make sense to have a 2-step join, just like in Slack? then the participants can choose to join as listeners; i.e. click on the room, see the bottom menu and then select the join mode
from clowdr-web-app.
Yes, I think this would be fine.
from clowdr-web-app.
This results in the silent observation problem mentioned above. It is acceptable in slack because the expectation is you know who is in the organisation. I don't think this is appropriate for a public conference environment. At a physical event, you wouldn't expect someone to be covertly listening in to a group conversation by standing on the other side of a room with a long range mic!
from clowdr-web-app.
Maybe I misunderstood the proposal. I thought we were just talking about a two-step process to join where the first step was choosing between A/V off and A/V on.
from clowdr-web-app.
Unless you meant not to show the room (video/audio/etc) until after the type of join has been selected? Which isn't like Slack's I don't think. That would be more like Zoom's behaviour.
from clowdr-web-app.
@bcpierce00 Okay yeah that's Zoom's model not Slack's.
from clowdr-web-app.
Related Issues (20)
- Occasional difficulty returning to chat room from e.g. private chat HOT 2
- UserStatusDisplay is broken HOT 1
- Relax 1000-user limit on text chats HOT 13
- Make recordings available only to logged-in participants HOT 2
- Embedding videos attached to Program Items HOT 4
- New UI Default Behavior HOT 1
- Backend repo migration HOT 3
- Registration Screen Not Scrolling in Firefox on Mac HOT 2
- Add a "test audio" button for breakout rooms
- Chat messages are too tall HOT 1
- Split bar between video/chat portion of event page is a little confusing
- Time in the chats missing AM/PM, creating confusion ! HOT 1
- Sidebar ideas
- UI nits
- "Presence"
- Clicking a link in a breakout room causes user to leave chat HOT 1
- Way to search by user flair
- Topic lines/dynamic room names
- Subtitle editor won't allow time codes to be corrected HOT 1
- Subtitle editor defaults to black-on-black mouseover text HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from clowdr-web-app.