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

Mobile web support is now unusable #14962

Closed
ara4n opened this issue Aug 14, 2020 · 7 comments
Closed

Mobile web support is now unusable #14962

ara4n opened this issue Aug 14, 2020 · 7 comments
Labels
A-Mobile O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Z-Experimental Z-Platform-Specific

Comments

@ara4n
Copy link
Member

ara4n commented Aug 14, 2020

It used to warn you to install mobile web, but then be vaguely usable (but dog slow). Nowadays following a event permalink looks like this:

@t3chguy
Copy link
Member

t3chguy commented Nov 12, 2020

So this is because of #7378

@nadonomy
Copy link
Contributor

+1'ing this, this is heavily broken if e.g. someone shares a link to a room with you: #22259

I believe this should be triaged as S‑Critical (given how broken the UI is) and O-Frequent (given it happens every single time).

@lampholder is the original rationale for #7378 still valid?

@lampholder
Copy link
Member

I'm not sure I have any useful context on this, sorry.

I think we wanted deep links to render on phones (so people could read the contents in the web view), only prompting people to download the app once they tried to interact with the room, but I'm not certain.

But https://riot.im/app isn't a deep link, so I don't know what 2018 me was talking about. Maybe the intercept page was just confusing folks by telling them to set a custom server to matrix.org when it is often the default (and is always the default on https://riot.im/app or https://app.element.io)? I'm just guessing now, though.

@nadonomy
Copy link
Contributor

I think we wanted deep links to render on phones (so people could read the contents in the web view), only prompting people to download the app once they tried to interact with the room, but I'm not certain.

The problem is this means committing to a responsive web reading experience, which I'm not sure we can do right now. Will dig further.

Maybe the intercept page was just confusing folks by telling them to set a custom server to matrix.org when it is often the default (and is always the default on https://riot.im/app or https://app.element.io/)? I'm just guessing now, though.

Yeah this sounds fair, we can revisit this and consider how we can be smarter pulling details from config.

@turt2live turt2live added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Jun 13, 2022
@Greenheart
Copy link

Greenheart commented Dec 20, 2022

Is there a good workaround for this in the mean time?

I've tried using matrix.to links to work around this issue, but got user feedback that it was too confusing for people to have to select between the different Matrix clients (plus understanding the protocol matrix in the first place).

For my use case, I want people new to Element and Matrix to be able to click a link and get straight into a public chat room where they can read on the web, and potentially create account + install native apps if they decide to participate more actively. This works well for desktop users, and sharing direct links to Element web is great for that.

However, for mobile users it looks like this:

@paboum
Copy link

paboum commented Apr 30, 2023

Is there a good workaround for this in the mean time?

For my similar usecase https://github.com/cinnyapp/cinny seems to be the best workaround.

@t3chguy
Copy link
Member

t3chguy commented Jul 13, 2023

Closing in favour of #9814

@t3chguy t3chguy closed this as completed Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Mobile O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Z-Experimental Z-Platform-Specific
Projects
None yet
Development

No branches or pull requests

8 participants