New chat ux on mobile

Contribute UX

AI-generated summary

Users are reporting issues with the new mobile chat UX, particularly around channel navigation and layout inconsistencies. Moin describes confusion when clicking a channel, as the chat opens below the screen, requiring scrolling to view messages. They also note the channels list appears duplicated, and the chat interface jumps when the Chrome URL bar is hidden or shown. JammyDodger confirms the issue, mentioning it took them time to locate a message. Benjamin_D questions whether the issue is browser or device-specific, while JammyDodger notes it works normally on other sites, suggesting a site-specific problem. j.jaffeux acknowledges the issue was due to a misconfigured meta instance and confirms it’s now fixed after a refresh.

1

I just want to report my confusion with the new interface.

When I clicked on the channel name I thought nothing happened, because the channel was opened below my screen.

_20220702_082210
_20220702_082210720×1248 53 KB

_20220702_082414
_20220702_082414720×1248 45.3 KB

Then I had to scroll through all messages to read the new one. After some testing I noticed that this is not what is shown directly after you click a channel.

I also noticed that before choosing a channel the channels are shown twice.

_20220702_084729
_20220702_084729720×1247 45.9 KB

When I scroll to the bottom and click the second “community” I can see the chat on my screen. But the position is at a point where older messages get shown. So after 2 seconds I have to start scrolling at the first message.
_20220702_085614
_20220702_085614720×1248 90.4 KB

By the way the the chat part jumps everytime after the url bar in chrome is hidden or unhidden.

_20220702_085923
_20220702_085923720×1248 90.9 KB

_20220702_085852
_20220702_085852720×1248 81.6 KB

Here you can see the different distance between the private chat and the channel.

3 Likes
Introducing Discourse Chat (BETA)
2

I tripped over this this morning. It took me a good half hour to find @not-ethan’s message in the community channel. :slightly_smiling_face: I’m not sure it’s intentional, as it doesn’t happen on all sites, but I’ve not tracked down the reason yet.

2 Likes
3

How does it work (on these sites)? Could it be browser/device related?

4

It works as usual on other up-to-date sites, even still using my Android/Chrome phone, so there’s something different here. I’ll upgrade my test site and have an explore.

1 Like
6

Sorry that was my bad, forgot to update our meta instance. It should be all good now (be sure to refresh), thanks for the report.

7 Likes
7

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.