Posts Tagged: buttons


10
Jun 08

Consistency within and between devices

“It’s worth repeating that you should not design your software to be consistent across devices. You should design your software to be consistent with the device it runs on. Your users are unlikely to use your software on many different handsets. When your software runs on an old Sony Ericsson phone, it should use the hardware Back key down to the left. When it runs on a Nokia Series 40 it should use the softkey back to the right.”

variousmenus_thumb

Link: Muscle memory (sender11.typepad.com)


27
Aug 07

One handed or two?

iPhone input-related articles keep rolling on in – this one from CNET is an interesting discussion on one-handed vs two-handed operation.

“The smart phones that most people are familiar with—the Nokias, BlackBerrys and Treos—only require one hand for basic operation. Obviously, typing on the QWERTY keyboards used by most of those devices is a two-handed operation, but navigating through the menu, looking up a contact, and using countless other functions only requires a single hand. “Everyone is still trying to make a one-handed product,” Rolston said. “It’s the easiest way to distinguish a truly portable device from a workstation. Handhelds are about doing something else (while using the handheld), they fit within the context of people’s active lives.””

Link: Coming to grips with the iPhone’s design (news.com.com)


20
Jun 07

The iPhone’s lack of haptic feedback

“If there is a billion-dollar gamble underlying Apple’s iPhone, it lies in what this smart cellphone does not have: a mechanical keyboard. As the clearest expression yet of the Apple chief executive’s spartan design aesthetic, the iPhone sports only one mechanical button, to return a user to the home screen. It echoes Steven P. Jobs’s decree two decades ago that a computer mouse should have a single button. (Most computer mice these days have two.) His argument was that one button ensured that it would be impossible to push the wrong button.”

Link: That iPhone Is Missing a Keyboard (nytimes.com)


29
Nov 06

Novel Samsung camera user interface

Samsung’s just come out with a couple of cameras in their new NV line that use their “Smart Touch” UI. Instead of the standard hardkeys + navigation key provided on most cameras, the screen has a set of unlabelled buttons to the right and below the screen and a zoom rocker switch. The controls are used as sliders and buttons are to ‘triangulate’ and then select options on the screen.

DPReview wrote: “Virtually all settings can be changed with just two button presses using a system that – once mastered – is incredibly fast and powerful. It’s not perfect, but it’s a big improvement on the pages and pages of menus it replaces.” (see the review for video of the UI in action)

DCRP Review wrote: “This unique user interface sometimes simplifies using the camera, and other times complicates it. Changing things like resolution and metering are easier than ever, while other things (such as deleting a photo) are more of a chore than they would be if the camera had a dedicated button for it. Sometimes the UI was very frustrating. The buttons on the right side of the LCD are right where your thumb rests, making them easy to press accidentally. When playing back photos, the buttons are too sensitive, making it very easy to race past the photo you’re looking for. Other times the buttons aren’t sensitive enough, such as with the playback zoom feature, which is very sluggish.”

PhotographyBLOG wrote: “Initially I found Samsung’s touch sensitive smart button system to be more revolutionary than effective, but once I’d discovered the Hide option and used it for a while, it became a lot more intuitive, making the various menu options much more accessible and speeding up the operation of the camera. It’s a very brave step by Samsung as it may put some buyers off (particularly as it takes some time to get used to), but on the whole it’s also a great idea.”

Link: NV10 (samsungcamera.com)


28
Oct 06

Pros and cons of non-mechanical buttons

Design Sojourn talks about the advantages and disadvantages of non-mechanical buttons.

““Static” buttons on the other hand have issues with feedback. Nothing moves, so there is no action and thus no reaction. Therefore designers that use “static” buttons need to employ a host of other feedback elements, like beeping sounds or lights. This is a very software driven interface and hence prone to software based problems. (Remember the blue screen of death?) If there is even a slight lag in response time, you would leave users wondering if they hit that button hard enough or if the angle of contact is even correct.”

Link: A petition to bring back buttons on phones? (designsojourn.com)