They copied the tab bar, and made it worse? Why would you encourage designers to hide labels? Why would you hide the bar when scrolling? So much confusion.
Absolutely supporting your opinion.
Actually they also have guidelines for the bar with labels. And hiding the bar when scrolling / not needed is quite often used in popular apps.
A hamburger menu is also popular, does not make it a good idea. I did not know about or find the guideline for a bottom navigation with labels, where did you see that?
Under the "Style" heading
Style each action according to the following conditions:
- When the view is in focus, display that view’s icon and text label
- When there are only three actions, display both icons and text labels at all times
- If there are four or five actions, display inactive views as icons only
Oh okay, guess I was visual-focused :-). Still a bad idea for a go-to element though :/
I wouldn't want to start pointing fingers about "copying" in the mobile interface biz, as everyone's equally guilty. And frankly, if somebody develops a better UI pattern, why shouldn't it be adopted elsewhere?
But I agree that Google's UX leaves a lot to be desired. Material Design was a welcome facelift, but they failed to address many of the fundamental issues with their UI – and this solution feels tacked on at best :/
totally agree your opinion
Nice addition, but don't you think that the software buttons are too close to this new navigation bar? I predict so many wrong button presses :D
We designed a bottom navigation to our Android app and it's been out for six months now. No complaints from customers about wrong button presses. That doesn't rule out the possibility though.
This is the fundamental problem with a navigation bar on the bottom of an Android app. This is a massive UI tradeoff in the operating system: commonly used universal actions on the bottom of the screen exist at the expense of Android apps being able to use the same area of the screen effectively.
The reason why the pattern works at all on iOS is that there are no software buttons to compete with.
I've tried it on Outlook, Google Photos, Google+ and there aren't any problems with the software buttons.
I was thinking the same thing, but after using Instagram for years now, I've never once had an issue with their tab bar on the bottom. In fact, I welcome it because my thumb can actually reach them on these damn huge phones.
Now you have the pleasure of 3 app menus – hamburger, kebab and tab bar – all within one screen. What a deal!
Nickname for the little triple-dot icon that usually denotes an overflow menu, but sits on its own on Android as some kind of screen-specific menu.
Brilliantly, whilst poking around Google's design guidelines looking for an official name for the kebab menu, I came across this little nugget:
Menus should not be used as a primary method for navigation within an app.
I think it's good to have flexibility in the UI solutions that are available to us. Each one of these has a specific use case they address. No one solution is perfect for everything.
The way I understand it is:
- Hamburger: Major sections in a larger app
- Tab Bar: Sub-sections within a view, to split content types for instance
- Kebab: Contextual actions for the current view (refresh, help, etc.)
It is good for designers and users as well - you will have very similar patterns on Android and on iOS and it will be easier for you to design / use apps on these platforms: bottom navigation (Android) as an alternative to tab bar (iOS), tabs (Android) as an alternative to segmented control (iOS).
That's what happens when manufacturers keep making phones bigger than 5".
always curious...how can android users reach the top bar (when switching between diff tabs happens a lot in some apps)
In most apps, you're able to swipe between the tabs on the top bar by swiping left and right, so there's no need to reach up :-). It's one of my favorite parts of Android, actually—I'm sad that they recommend against lateral swipes when using the bottom nav.
Google used to want make a different, now they change their mind.
Really surprised by this
So is this a completely new component in their guidelines?
Finally they changed the top navigation.
Is it just an Android thing to not move laterally through views?
On iOS, Google Photos moves laterally through views when using the bottom tab bar.
Yeah, I've got to say, as I looked at those two examples, I thought, "The one they're telling designers not to do gives the content a greater sense of place and permanence. But the other one: How shiny! Wow!"
Finally some good changes for UX! For too long I couldn't understand why would they put top nav when is so hard to reach with nowadays phones. Still waiting for the upside-down list scrolling....
Has anybody been using this? Haven't really seen it in any app.
I never had an issue with the tabs being at the top because you could swipe left and right, so you didn't have to reach for them. But now this...
"Using swipe gestures on the content area does not navigate between views."
I guess the swipe is unnecessary if the buttons are reachable now, but I still found it easier to navigate by swiping, as I could keep my thumb in the same place. Now I have to move my thumb to go to each section.
At least this means they acknowledge not everyone has massive fingers :)
Someone on the team finally read: How to Design for Thumbs in the Era of Huge Screens
that's a lot of UI buttons on the bottom of every android device.
Get the pitchforks ready, boys.
They added a new component but refuse to update the rest of the guidelines.