You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our experience many people (want to) use the schedule as a gateway to the content: They open the schedule, look for a specific session, read the description and are then expecting a) the content to be there or b) a button to the correct livestream/BBB.
This feature, admitedly is not without its problems: Any button there will send me to the correct stage but in many cases at the wrong time, i.e. it'll send me to the livestream no matter if the talk is currently taking place there or not. On the other hand: If I go to a room at a conference before or after the talk I want to see, it won't be there – so I guess people will figure that one out by themselves.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion!
We're currently working on tighter schedule integration, and better navigation will be part of that.
We share your concerns. We already have information on what sessions are actually live (as part of #257), so we can show the appropriate links or buttons at the right time and inform the user on what to expect when they navigate to the room.
In our experience many people (want to) use the schedule as a gateway to the content: They open the schedule, look for a specific session, read the description and are then expecting a) the content to be there or b) a button to the correct livestream/BBB.
This feature, admitedly is not without its problems: Any button there will send me to the correct stage but in many cases at the wrong time, i.e. it'll send me to the livestream no matter if the talk is currently taking place there or not. On the other hand: If I go to a room at a conference before or after the talk I want to see, it won't be there – so I guess people will figure that one out by themselves.
The text was updated successfully, but these errors were encountered: