Archive for the ‘interfaces’ Category

iPad User Interface

Thursday, July 22nd, 2010

Continuing on the iPad UI tip, I came across this nice summary of Apples Human Interface Guidelines today on www.uxmag.com, well worth a read when thinking about developing applications for tablets.

Apple’s Human Interface Guidelines for the iPad outline how to create user interfaces optimized for the iPad device. According to Apple, the best iPad applications: downplay application UI so that the focus is on content; present content in beautiful, often realistic ways; and take full advantage of device capabilities to enable enhanced interaction.

The overview of iPad user experience guidelines listed below is © 2010 Apple Inc. More details on these guidelines and further information on developing for the iPad can be found in Apple’s Human Interface Guidelines for the iPad.

Support All Orientations
Your application should encourage people to interact with iPad from any side by providing a great experience in all orientations. The reason is that people don’t view the device as having a default orientation, because they don’t pay much attention to the minimal device frame and they’re unconcerned with the location of the Home button.

Enhance Interactivity (Don’t Just Add Features)
The best iPad applications give people innovative ways to interact with content while they perform a clearly defined, finite task. Resist the temptation to fill the large screen with features that are not directly related to the main task. In particular, you should not view the large iPad screen as an invitation to bring back all the functionality you pruned from your iPhone application.

Flatten Your Information Hierarchy
Although you don’t want to pack too much information into one screen, you also want to prevent people from feeling that they must visit many different screens to find what they want. In general, focus the main screen on the primary content and provide additional information or tools in an auxiliary view, such as a popover.

Reduce Full-Screen Transitions
Instead of swapping in a whole new screen when some embedded information changes, update only the areas of the user interface that need it. When you perform fewer full-screen transitions, your application has greater visual stability, which helps people keep track of where they are in their task.

Enable Collaboration and Connectedness
Think of ways people might want to use your application with others. Expand your thinking to include both the physical sharing of a single device and the virtual sharing of data.
Add Physicality and Heightened Realism
Whenever possible, add a realistic, physical dimension to your application. The more true to life your application looks and behaves, the easier it is for people to understand how it works and the more they enjoy using it.

Delight People with Stunning Graphics
The high-resolution iPad screen supports rich, beautiful, engaging graphics that draw people into an application and make the simplest task rewarding.

De-emphasize User Interface Controls
Help people focus on the content by designing your application UI as a subtle frame for the information they’re interested in. Downplay application controls by minimizing their number and prominence. Consider creating custom controls that subtly integrate with your application’s graphical style. In this way, controls are discoverable, but not too conspicuous.

Minimize Modality
iPad applications should allow people to interact with them in nonlinear ways. Modality prevents this freedom by interrupting people’s workflow and forcing them to choose a particular path.

Rethink Your Lists
Consider a more real-world vision of your application. For example, on iPhone, Contacts is a streamlined list, but on iPad, Contacts is an address book with a beautifully tangible look and feel.

Consider Multifinger Gestures
The large iPad screen provides great scope for multifinger gestures, including gestures made by more than one person.

Consider Popovers for Some Modal Tasks
If you use modal views to enable self-contained tasks in your iPhone application, you might be able to use popovers instead.

Restrict Complexity in Modal Tasks
People appreciate being able to accomplish a self-contained subtask in a modal view, because the context shift is clear and temporary. But if the subtask is too complex, people can lose sight of the main task they suspended when they entered the modal view.

Downplay File-Handling Operations
Although iPad applications can allow people to create and manipulate files and share them with a computer (when the device is docked), this does not mean that people should have a sense of the file system on iPad.

Ask People to Save Only When Necessary
People should have confidence that their work is always preserved unless they explicitly cancel or delete it. If your application helps people create and edit documents, make sure they do not have to take an explicit save action.

Start Instantly
iPad applications should start as quickly as possible so that people can begin using them without delay.

Always Be Prepared to Stop

Like iPhone applications, iPad applications stop when people press the Home button to open another application.

More details on these guidelines and further information on developing for the iPad can be found in Apple’s Human Interface Guidelines for the iPad.

UX Magazine

Too early for the new to feel old

Wednesday, July 21st, 2010

A conversation with our UI designer earlier today got me thinking about how easy it can be to fall into the trap of conforming to a certain design or interface aesthetic once you see a few incarnations of something. In particular, most of the iPad applications that have been launched in their thousands over the past couple of months seem to do one of the following:

1) Use old iPhone design principles in a bid to get an application out there on a new platform ASAP.
2) Try and create a brand new shiny aesthetic but without much thought for what this new platform is and more importantly how people will use the content made available.
3) Take one of the early prototypes that were developed (think Wired, Sports Illustrated etc) and then merely pinch those ideas.

This has been getting a load of airplay today, a new social magazine application from FlipBoard. I like the feel of this, the transitions between pages and between content. I like the way they’ve taken a problem (lists and lists of updates, news, photos, lists and lists and lists) and attempted to solve it through UI Design, creating something brand new but oddly familiar.



As Anna quite rightly pointed out, this is something new, its too early to settle for either some new accepted norm for an application, a set of rules that we automatically abide by. This is a phase to be playing, experimenting, building UI’s that may be baffling, challenging and indeed may fail and fall by the wayside.

But that’s why we do what we do, right?

Meta Products and the Internet of Things

Tuesday, June 22nd, 2010

The Internet of Things is a fascinating concept. The idea that all the data that we’re collecting and generating online, having a real world impact in our day to day lives, and vice versa.

IBM created this short video by way of an explanation earlier in the year:

Just came across a blog by Dutch agency Boorieland regarding Meta Products, the development of ideas for physical products that utilise the web for their data. There’s something fantastically exciting about the opportunities surrounding this matrixing of complex services.

Minority Report?

Thursday, February 18th, 2010

Taken from the motherboard blog:

The latest and perhaps realest step forward in the realm of lazy, mouse-free interfaces arrives courtesy of John Underkoffler, who happened to be working in theMIT Media Lab alum when the producers of Minority Report came through looking for face-melting ideas for their movie. They hired him and his idea, and after the years-long, caffeine-fueled sloppy intercourse of Hollywood and Silicon Valley, he and his company Oblong have emerged at the TED conference with an actual spatial operating system.

g-speak overview 1828121108 from john underkoffler on Vimeo.