June 11th, 2014
It’s not uncommon that an interaction for an app on a mobile device is completely different than a desktop. Could inline help be the answer to communicating the necessary action? It’s not so easy as that as Luke Wroblewski points out in this week’s UIEtips. You still have to surface the hidden interface.
Thinking about mobile design first is Luke’s mantra and what he’ll focus on in his full day workshop at this year’s User Interface Conference, October 27-29 in Boston. Explore how Luke will shift your thinking beyond the desktop.
Here’s an excerpt from the article:
A common way to provide relevant bits of guidance inside an application is through inline help. Inline help is positioned where it’s most useful in an interface and made visible by default so people don’t have to do anything to reveal it. This makes it an effective way to tell people how to use an interface. But what happens when those instructions vary by input type.
Read the article: Customizing Help and Tips by Input Type.
How do you and your team create interfaces that work with different screen sizes and input types? Leave us a note below.Tweet