UX Risks with EC + JITSI group calls

### Your use case

**Giving the ability to use either EC or JITSI in group calls UX concerns:**

1/ Giving ability to choose between the two options will not be clear for all users. What is Jitsi? What is Element call? It is also super uncommon to give the ability for users even at Beta stage. The pool of users using this will be larger with much much less tech savy users.
Currently, the definition of Labs VS Beta seems unclear. I however recommend for Beta stage to be considered as "almost ready" feature. Labs for experimental stage, allowing active development of a feature in a progressive manner.

Typically Beta release are to uncover unknown issues from users. In this case, there are a large range of UX issues we are already aware of. This means that rather than uncovering new user pain points, user testing in beta will only repeat the points highlighted in this issue.

2/ What will happen if someone uses Jitsi and another doesn't? How will users perceive this? One might be waiting in Jitsi without full awareness that the other is in EC. How will this make users feel?

3/ When a Jitsi call is still ongoing, users see "ongoing call" when hovering the video button. Because of the current widget behaviour with Jitsi, it is only possible for Admin users to remove the widget to end a conference call. Meaning that if the Jitsi widget is not removed, the call will never be ended and so users will not be able to start a new call with either EC or Jitsi.

4/ Non admin users have to switch on the EC option in room settings to be able to join an EC call. This is hidden and unclear that these user types have to take this extra step for it to work. This is confusing for users as they are not guided through correct steps. This is damaging the XP of joining the EC beta for these users.

5/ Element Call is not implemented on mobile platforms. There are obvious UX implications on having a feature available on one platform and not another.

6/ SFU delivery is a long way in meaning that if EC is released in Beta, the risks on poor UX will be increased and consequently, this will diminish the credibility of the product for a wider audience and for longer period of time.

7/ There will be not 2 but 3 completly different tech stacks and User experiences available to Element users for an extended period of time. Matrix call, Element call and Jitsi resulting is a fragmented and confusing UX for users

No files, tests, or entry points are named. Start by reviewing the group-call UX flows for provider selection, mixed Jitsi and Element Call usage, call ending, room settings, and mobile availability; done means the concerns have a decided, consistent UX direction.

Written by the indexing model from the issue text.