I'm beginning to exhibit raging hatred of the right nav concept... Firstly.. Ergg. two settings is confusing (site and user) - they should be the same page and there is no reason why they can't be. It would be great if when logged in the settings page morphed from device specific to user specific. Would be great to be able to activate alpha on all my devices. In terms of a right nav, the more I think about it and having played with a prototype I knocked up, the more I think a right nav is bad. Although it seems to be becoming an established pattern it seems like an easy option that in my opinion is badly implemented. We can do better and should lead by example. For one I never touch the Facebook one... it just doesn't come natural. I also don't like the idea of 2 menus. I wonder if we could envision 2 stacked menus that can be toggled between and persist when selected. To quote http://www.upassoc.org/upa_publications/jus/2011august/faulkner2.html "... Kingsburg and Andre carried out two studies with 16 users and found in both of their studies that selection from a left-hand menu was faster than from a right-hand menu (2004). However, their research also showed that selections were best done from the same panel, whether that was on the right or left. Thus it is better to have a single design, either on the left or the right, rather than a mixed navigational method that requires the user to select from both left and right panels (Kingsburg & Andre, 2004). This is hardly surprising and is both predicted and supported by Fitts’ Law. (1954)." The thing that bugs me most is that when you move your finger over the left hamburger button and press it the page moves to the left. Your finger is still above the button. This doesn't apply to the right menu. Your finger is now above something else. This to me is very jarry and always feels icky. It still leaves the question of where things such as watch star, talk page link, edit, move and delete buttons go. The bottom would make sense for an app, but position fixed is buggy in the majority of current mobile browsers and we will need a fallback of some sort. On Thu, Apr 25, 2013 at 5:57 PM, Maryana Pinchuk <mpinchuk(a)wikimedia.org> wrote: