element-hq / element-hq/element-call

UX for participants who can't connect

Open
#1,251 0 comments 0 reactions 0 assignees View on GitHub
O-Occasional T-Enhancement X-Needs-Design
Dominant language
TypeScript
Stars
996
Forks
215
Avg merge
1d 6h
Merged PRs (30d)
54

Description

### Your use case

#### What would you like to do?
Work out what our UX should look like for participants who are trying to join but not successfully publishing media.

#### Why would you like to do it?
It seems like at the moment, this is a grey square with no feedback which leave the user not really knowing what's going on.

#### How would you like to achieve it?

### Have you considered any alternatives?

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by reviewing the participant join and media-publishing flow; done requires an agreed UX for participants who cannot connect or publish media, followed by the corresponding implementation.

Written by the indexing model from the issue text.

Assessment

Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.