One of the most common implementations of menu views has been the “side drawer,” “basement,” or “side menu” made popular in apps such as Facebook and Path. When a user taps the “Hamburger” icon to open a side menu, the main screen slides to the right (or left in some implementations) to reveal another screen below.
Less than one year ago, most of my clients were requesting iPhone app design. Today they are still asking for iPhone app design but many also say, “Do you do Android, too?” Most of them plan to start with one platform, see how things go, and then decide whether to invest in the second platform. This roll-out strategy is often tied into engineering costs. Since few developers possess the coding skills required for each platform—Objective C for iPhone and Java for Android—it’s often necessary to hire two development teams. But what about design? Would I, too, have to do twice the work when designing for the iPhone and Android? And what will happen if the Windows, Palm, and Blackberry app stores take off? Would I have to do five times the work?
An ever increasing range of mobile phones are appearing on the market, each with their own features, designs and interfaces. Our extensive experience of working with a wide range of phones suggests that, despite their many differences, there are some user interface requirements common to all mobile phones. These requirements are presented as guidelines below.
After wearing my Apple watch daily for the past two+ months, I've found myself wishing for a simpler interaction model for moving between content and apps. Here's what I'd propose and why.