Yes…notifications often take a few seconds to show themselves. Let’s not kill the other menus with that sort of response, too.
1 Like
How it is now is fine.
The notifications menu is its own distinct thing - it isn’t cluttered up with other menu options that I’ll have to look past and make sure I don’t accidentally click.
Maybe the user menu is “lame” but it also keeps those options I use rarely out of the way of the options I use waaaaaaaaay more often.
I disagree that it is on mobile, I would way prefer
Swipe right to see notifications
Swipe left to see navigation
Also user drop down is weird
2 Likes
Oh mobile? Yeah, that’s different.
2 Likes
That is a lot of hidden magic there. How does one teach the mobile users of such?
I’d much rather have one menu when you swipe left or right. It can contain the menu, profile, search, what-have-you. You simply click the section and it expands the menu for that action.
Yeah, but mobile is generally not fine.
1 Like
not really … click hamburger you see an effect showing its sliding stuff in from the right to the left, swipe left is just a discoverable shortcut, commonly used on slack, gmail and plenty of other mobile apps.
Not for me…
Android 5.0.1, latest version of Chrome
Plus slack doesn’t do what you say it does… (at least on Android). The swiping moves between tabs that are already visible. It isn’t bringing out a menu that didn’t have any prior existence previously. All of the swiping features in slack, have buttons that are visible and perform that action as well (from what I can tell). There isn’t any magic that you have to guess to find notifications (I was getting the suspicion that we’re removing the buttons in Discourse… is that not true).
It has always been my understanding that we’re merely talking about swipe-gestures as an alternative to clicking a button that will be visible regardless.
Going back to the hamburger menu on the left: I don’t know about iOS, but on Android there’s definitely a trend of slide-in menus from the left, always discoverable via a visible hamburger bar.
And the menu tends to be a content-portal.
Note: These all had a visible hamburger icon in the top left corner before I clicked/swiped to reveal the menu.
I think this convention makes a lot of sense for Discourse as well.
Interestingly, none of these has a slide-in, full height menu on the right.
5 Likes
The left-swipe navigation drawer on android is a well-established standard. Google has detailed design guidelines here:
However, they typically contain many far fewer items than Discourse’s hamburger menu. ie. <10 so that no scrolling is required. Slack have just changed their interface, but the previous version had a nav drawer for channels, contacts and groups.
The current meta.discourse hamburger has 30 items, which is more than I have in my Slack nav drawer (~20). It’s an uncontrollable number of course, since people can run forums with 100 categories if they want. On my site, it’s only 14, but that’s without including sub-categories (which I’d like to see, as it happens).
+1 for consolidation of Notifications and avatar menu. It would be very clear if the hamburger on the left was for “places” and the avatar on the right was for “me” Again, this is how the previous version of the Slack app did things. (although they had no dedicated notifications area, just (1) next to channels/people who’d @mentioned you)
I think @erlend_sh’s mockup gets it just right (although I’d keep search as a glyph rather than a text box, to conserve space on mobile)
Another vote for left-hand slideout. It’s quickly becoming the standard, at least on mobile.
Maybe this is best for a separate discussion, but I’d also be in favor of removing/slimming down the number of categories listed. Maybe its just me, but I never find myself clicking them… there are other easier paths to find any given category. Instead, maybe combine all the useful “feature pages” and user menu items on the hamburger slideout, and make the user avatar handle notifications a la Rewphus.
1 Like
Okay, ignore me then 
I mis-read something along the way. Sorry for the interruption.
Edit: As per @codinghorror’s suggestion, I started a new thread to discuss this more radical change further.
5 Likes
We are done here for now, implemented… closing.