issue: menus are not always immediately apparent
suggestion: style menus like sidebars (outlines and backgrounds)
issue: user menu elements on mobile are jammed against left edge
suggestion: add left padding
issue: content and comments are too narrow on large/wide displays
suggestion: add option to set min and max widths relative to viewport (CSS VW)
issue: main menu (from hamburger button) elements on mobile/narrow displayed as block is unsightly
suggestion: elements should be inline-block until they cannot fit on one line
issue: comment action icons are unnecessarily hidden
suggestion: show all comment icons persistently (could be grouped as [up/down/reply] on left, [message/flag/block/fav/source] on right; could be a user profile option to show/hide additional comment options persistently)
issue: message notification (bell icon) often indicates unread count when all messages are read
suggestion: fix
issue: auto-refresh on posts causes elements to move down as reading when scrolled
suggestion: implement option to disable auto-refresh OR move scroll position down correspondingly to total height of dynamically loaded post elements
issue: (if above feature implemented) must refresh page if auto-refresh disabled
suggestion: add soft-reload button (reloads posts)
issue: [subscribed|local|all] default from user profile doesn’t work (always selects local)
suggestion: fix
issue: no function to block a specific community from your feed
suggestion: add function
issue: notifications view has no stateful awareness of viewing mode [unread|all] or [all|replies|mentions|messages]
suggestion: add stateful awareness to enable browser <|> navigation
issue: replying to inbox comment/message does not display after submitting reply
suggestion: display reply to comment after submitting reply
issue: [show context] from inbox comment does not display immediate parent comment
suggestion: [show context] from inbox comment should display immediate parent comment
issue: when viewing context from comment on a non-local instance, you are not authenticated and cannot reply from context
suggestion: implement cross-instance authentication OR link to context in the currently-authenticated instance
issue: [next] buttons have no stateful awareness (displays an empty page when clicked from the last page in a set)
suggestion: [next] should be statefully aware of page and be disabled when viewing last available page
issue: when inbox messages appear as a notification, there should be a button to mark them as read
suggestion: add function
issue: inbox messages are only marked read when explicitly clicking [read] checkmark button
suggestion: messages should be marked read when replying or navigating to context
Hope this helps make some improvements to the UX! :)
EDIT another one while I’m thinking of it: it would be nice for the top toolbar to be fixed at the top so you don’t need to scroll back up to use it.
I have always HATED the auto refresh features so many sites enable by default. Twitter does it, Facebook does it, Reddit does it (sometimes), etc. I can’t stand it. I want to read what I scrolled down to not something that just randomly popped up. Or worse some of them do this weird thing where it scrolls me further down and automatically hides the previous ~5+ posts or something like that. Super annoying.
This type of thing should be a user setting, not a site wide setting, IMO.
Also, there should be a user setting (maybe I missed it?) to reposition the new comment box to the top of the page instead of the bottom.
Yeah, I gotta be honest, it works really poorly here, especially when viewing all/hot. It’s just constantly loading new posts and pushing down and off-screen whatever you’re trying to read or click. It’s frankly unusable.
This type of thing should be a user setting, not a site wide setting, IMO.
Yep, this is exactly what I meant. Just the option to disable auto post loading so you see whatever posts where loaded at the time you initially opened the page. If I want to see new posts, I can hit reload myself.
To get these in front of the devs, you could open an issue in the lemmy-ui repo: https://github.com/LemmyNet/lemmy-ui/issues
Yeah they are really busy right now, so if you want them to get seen you’ll want to merge them into what is/isn’t there in the github