Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better duplicate session UX #4366

Closed
marcoambrosini opened this issue Oct 14, 2020 · 5 comments · Fixed by #4374
Closed

Better duplicate session UX #4366

marcoambrosini opened this issue Oct 14, 2020 · 5 comments · Fixed by #4374
Assignees
Labels
Milestone

Comments

@marcoambrosini
Copy link
Member

marcoambrosini commented Oct 14, 2020

I find this warning annoying and most of the time useless. I always end up clicking "Join here" anyway.

Duplicate session
You are trying to join a conversation while having an active session in another window or device. 
This is currently not supported by Nextcloud Talk. What do you want to do?

So this is my proposal to improve this:

let's say that:

  • I have a tab open somewhere and I joined conversation A in that tab 1;
  • I have talk open in tab 2 and i click on conversation A there too;

CASE 1 (most of the time)

User is not participating to a call in tab 1

=> Just join the conversation in tab 2, without any warning and display the "You joined the conversation in another window or device." notice in tab 1;
We could also change the title of tab 1 into duplicate session so that if things get messy one can easily see at a glance which tabs are safe to close.

CASE 2

User had previously joined a call in tab 1

=> Show a warning that says that there's a call undergoing in conversation A in some other tab, and joining here would interrupt the call.

Do you see any drawbacks with this approach?

cc @nextcloud/designers

@skjnldsv

This comment has been minimized.

@marcoambrosini marcoambrosini transferred this issue from nextcloud/server Oct 14, 2020
@marcoambrosini

This comment has been minimized.

@jancborchardt
Copy link
Member

Seems like a good improvement – warning only when necessary.

It's then also needed to have this warning on mobile too, since currently you can end your own calls by opening the same conversation (even only the chat) on mobile, without getting informed why.


Of course the best UX would be if you could just view a conversation with as many devices as you like. And that opening a chat where you are already active in a call will show you the chat, but not interrupt the call.

@nickvergessen
Copy link
Member

#1587

@nickvergessen
Copy link
Member

It's then also needed to have this warning on mobile too, since currently you can end your own calls by opening the same conversation (even only the chat) on mobile, without getting informed why.

This is scheduled for when developers have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants