Google describes the navigation drawer very well in their design guidlines. and points out that
As the navigation drawer expands [...] The overflow menu with the standard action items for Settings and Help remains visible
Also Roman Nurik mentioned in a post some time ago that settings/feedback/... actions do not belong in the Navigation Drawer.
However, google started to break this guidline in their material design version of their apps. At least in Hangouts, Gmail, Google Maps ans some more.
So what's the current guidlines?
Should I put Feedback, Settings ans Help in the overflow menu or in the Navigation Drawer?
Navigation drawer guideline and Google+ post are written before Material design.
in majority of new Google apps these items are in navigation drawer. also in new Material design Navigation drawer guideline these items mentioned in navigation drawer.
Google's guideline regarding Settings location:
"When a navigation drawer is accessible from the current screen, place Settings in the drawer. Otherwise, place Settings in an action overflow menu."
http://www.google.com/design/spec/patterns/settings.html#settings-flow-structure
Related
Please image is given in the following link. What is the term or official term of this bar with the icons together?
It is the Android Navigation Bar.
You can find more info in the Material documentation.
Android navigation bar
The Android navigation bar in Android houses the device navigation controls: Back, Home, and Overview. It also displays a menu for apps written for Android 2.3 or earlier.
Just a final note.
Android 10 introduced a new immersive look which involves also the look, dimension and the behaviour of Navigation Bar.
I'm wondering if I should combine the material design Bottom Navigation and the Navigation Drawer.
As is understand there is always one item active in the Bottom Navigation Bar, but what if I choose to navigate to a page using the Navigation Drawer menu? How do I preserve navigation consistency.? The Bottom Navigation item will still be active even if I navigated to a different activity/fragment.
I was thinking about setting all Bottom Navigation items to inactive in case a user navigates using the Navigation Drawer.
Unfortunately, the lib I'm using (https://github.com/pocheshire/BottomNavigationBar) doesn't support this.
How does the Bottom Nav Bar coexist with the Navigation Drawer? What am I missing here?
Looking at the design guidelines, it's pretty clear that the navigation drawer is at a higher z-level (hence higher hierarchy). Think of bottom navigation as essentially a replacement for tab layouts. You can look at the Google Photos application as an example.
As the title suggests, my app uses a side menu using navigation drawer. I got inspired by this official google doc and its nav drawer can be toggled either by swipe from left to right or by clicking on modified home icon on top left of ActionBar.
When nav drawer is drawn, the drawer icon in Actionbar is replaced by back button which in change closes the drawer and returns actionbar to its original state.
But this is where I find problems. As in this different official google doc about material design it is clearly stated that drawer should be over actionbar covering it.
I checked e.g. gmail app uses the latter, i.e. drawer over ActionBar.
Should I follow guidelines #1 or #2?
"The wonderful think about standards is that there are so many to choose from." — Admiral Grace Hopper
I'll start by pointing out that the first link you referenced that talks about closing the drawer by clicking the icon is pre-Material Design. So my choice would be to go with the Material Design-specific recommendation.
Now take a look at this:
The Many Faces Of Google's Hamburger Navigation Drawer | Android Police
Material Navigation Drawer isn't even consistent within Google's own apps.
I think some UX people feel that there should still be a single-touch way to close the drawer in addition to the swipe. Looks like even the dev teams within Google can't come to a consensus.
So consider all your options, then do what makes the most sense for your app.
I would like to create my own Navigation Drawer
using the current Material Design for the Navigation Drawer.
A good example of this implementation is the YouTube app.
In the App the Navigation Drawer overlaps the Action bar and is not below the action bar like in previous implementations.
I've tried following some example from other people's tutorials but they fall short of what I want. I have included some of the implementations that I have tried. I do not want to use a Library,
I want to implement it . Is there currently a tutorial that applies the Material Design Patterns properly.
YouTube Navigation Drawer
http://www.google.com/design/spec/patterns/navigation-drawer.html#
I used https://github.com/chrisbanes/cheesesquare as a reference. However I came across this tutorial that provides a proper guide on how to create a material design navigation drawer whilist also handling the click events of menu items
https://guides.codepath.com/android/Fragment-Navigation-Drawer
http://www.androidhive.info/2013/11/android-sliding-menu-using-navigation-drawer/
Here is an example of Navigation Drawer which works superb. But I would like to have like in google gmail application that background is also moved to the right and not that navigation drawer gets over the background. How can i make this?
Gmail App Uses the Navigation Drawer. But what you are looking for is SlidingPaneLayout. This should come in Handy - http://www.survivingwithandroid.com/2013/10/android-slidingpanelayout-tutorial.html