Android apps that use an action bar no longer use an option menu button, which, in earlier Android versions, looked like a "hamburger button."
They might still have an overflow pop-up for commands that don't fit in the action bar. That's shown as three stacked dots. That depends on screen geometry and how the app has configured the action bar. Apps can avoid having an overflow pop-up and use, for example, a split action bar instead.
The article's main complaint isn't about the hamburger button per se, but the fact that it often pops out what in Android parlance is called a "navigation drawer." That's what's bad. And Google is pushing that idea as a replacement for a "dashboard" screen which was even worse, and is now deprecated as an official design idiom. But, as the article points out, a navigation drawer is just as much a nowhere-land as a "dashboard." Avoid it.
The article advocates a tab bar as an alternative. On Android, you have the choice of Tab objects that would show different Fragment objects, or a split menu bar. But, better still would be to make navigation an organic part of selection within the app. This has the added advantage on Android of not requiring different tab bar behavior on multi-Fragment layouts.
Some Android apps might have a hamburger menu leading to a navigation drawer, but that is probably due to iOS port-itis, not a deliberate idiom using Android UI elements.
Comments
Android apps that use an action bar no longer use an option menu button, which, in earlier Android versions, looked like a "hamburger button."
They might still have an overflow pop-up for commands that don't fit in the action bar. That's shown as three stacked dots. That depends on screen geometry and how the app has configured the action bar. Apps can avoid having an overflow pop-up and use, for example, a split action bar instead.
The article's main complaint isn't about the hamburger button per se, but the fact that it often pops out what in Android parlance is called a "navigation drawer." That's what's bad. And Google is pushing that idea as a replacement for a "dashboard" screen which was even worse, and is now deprecated as an official design idiom. But, as the article points out, a navigation drawer is just as much a nowhere-land as a "dashboard." Avoid it.
The article advocates a tab bar as an alternative. On Android, you have the choice of Tab objects that would show different Fragment objects, or a split menu bar. But, better still would be to make navigation an organic part of selection within the app. This has the added advantage on Android of not requiring different tab bar behavior on multi-Fragment layouts.
Some Android apps might have a hamburger menu leading to a navigation drawer, but that is probably due to iOS port-itis, not a deliberate idiom using Android UI elements.