Sender | Message | Time |
---|---|---|
16 May 2023 | ||
17:50:48 | ||
21:13:17 | ||
17 May 2023 | ||
08:05:32 | ||
21:11:58 | ||
18 May 2023 | ||
16:20:33 | ||
21:17:45 | ||
19 May 2023 | ||
Hi not sure if this belongs in here or the android room. I have to point out that the room join ux in element android currently is a nightmare. Let's play it through: I start in a space sind ele android defaults to using random spaces a room is in. I can't open the room directory from spaces so I need 2 clicks to get to the all rooms view. Then I need to click the search. However just inputing an alias won't get me anywhere since it tells me room not found. I need to click that I want to search the room directory. So we are at 4 clicks and 1 interaction now. In some cases I can now join however often I then need to change the server to be the respective server of the alias. Meaning at least 2 more clicks. Possibly even more. But it doesn't end here. I now click the room. I wait for the preview to load. Then I can click the join. It joins. However the popup disappears without feedback if the joined worked or not. I did 6 clicks and 1 interaction by now. Possibly even more. To check if I joined the room I need to go back to the roomlist. Another 2 clicks. Then I need to search the room in the roomlist. Do we really need to make joining rooms that hard? It feels like the intent is to jot join rooms using aliases on mobile. It smells sadly like a major dark pattern Design... Especially the join feedback would be nice but also just being able to quickly put the alias into the search and joining it without needing all the manual context changes would be appreciated. | 12:01:00 | |
I am posting this here since element wbe has a similar but slightly less horrible flow if you start in spaces. Room directory is only accessible from outside of spaces | 12:01:41 | |
This leads not only to friction imho but also complicates the flow massively for new comers. "why does the same button do different things depending on where I am at"? | 12:02:19 | |
* This leads not only to friction imho but also complicates the flow massively for new comers. "why does the same button do different things depending on where I am at?" | 12:09:00 | |
* Hi not sure if this belongs in here or the android room. I have to point out that the room join ux in element android currently is a nightmare. Let's play it through: I start in a space sind ele android defaults to using random spaces a room is in. I can't open the room directory from spaces so I need 2 clicks to get to the all rooms view. Then I need to click the search. However just inputing an alias won't get me anywhere since it tells me room not found. I need to click that I want to search the room directory. So we are at 4 clicks and 1 interaction now. In some cases I can now join however often I then need to change the server to be the respective server of the alias. Meaning at least 2 more clicks. Possibly even more. But it doesn't end here. I now click the room. I wait for the preview to load. Then I can click the join. It joins. However the popup disappears without feedback if the joined worked or not. I did 6 clicks and 1 interaction by now. Possibly even more. To check if I joined the room I need to go back to the roomlist. Another 2 clicks. Then I need to search the room in the roomlist. Do we really need to make joining rooms that hard? It feels like the intent is to not be able to join rooms using aliases on mobile. It smells sadly like a major dark pattern Design... Especially the join feedback would be nice but also just being able to quickly put the alias into the search and joining it without needing all the manual context changes would be appreciated. (edit Was typos related) | 13:04:47 | |
In reply to @mtrnord:midnightthoughts.spaceAlso just to make sure: matrix.to or similar are not an acceptable solution to the issue since it isn't always used. There are many cases especially on github where you only have the alias. So constructing the matrix.to link yourself is similar much clicks to do. | 13:09:50 | |
And it's not obvious to the user if they are new to matrix or element | 13:10:09 | |
17:38:35 | ||
22 May 2023 | ||
08:21:19 | ||
23 May 2023 | ||
08:11:14 | ||
21:41:04 | ||
25 May 2023 | ||
07:56:56 | ||
08:07:33 | ||
26 May 2023 | ||
16:47:06 | ||
27 May 2023 | ||
04:05:14 | ||
28 May 2023 | ||
18:59:20 | ||
29 May 2023 | ||
10:34:21 | ||
10:36:18 | ||
10:37:01 | ||
16:07:11 | ||
30 May 2023 | ||
06:26:42 | ||
08:13:57 | ||
09:25:01 | ||
11:52:07 |