&gt; That&#x27;s driven by screen size - there&#x27;s simply not enough screen real estate on a phone to label every button with words. It does have a legit discoverability problem, which most folks in UX acknowledge but don&#x27;t know how to fix, given other constraints of the media.<p>Some of the most effective solutions to this I&#x27;ve seen require solutions beyond visual representation. They address the problem through dimensions independent of viewport size and space.<p>For example, LukeW&#x27;s &quot;Don&#x27;t Divert the Train&quot; <a href="http:&#x2F;&#x2F;www.lukew.com&#x2F;ff&#x2F;entry.asp?1798" rel="nofollow">http:&#x2F;&#x2F;www.lukew.com&#x2F;ff&#x2F;entry.asp?1798</a> moves content from behind navigation and into the user&#x27;s already-occurring action stream. The button is removed entirely, as is the designer&#x27;s need to consider how communicative icons are for representing actions.<p>This requires a broader view of how features relate to each other through a design process that discovers other paths to successful behavior. Approaches like the hamburger menu, in addition to the usability issues you note, solve functional goals but have fallen out of vogue for their ineffectiveness at encouraging specific actions. Label-less icons, while attractive and convenient, suffer similar problems.  As getting users successful quickly is generally an important goal (before they&#x27;ve internalized your app&#x27;s unique visual language), the current trend of putting core functionality behind opaque symbols seems counterproductive.