Category Archives: Mobile Devices

Designing for mobile is a constantly evolving art, and we’re thrilled to have on the Locatrix team one of the best Interaction Designers in the business: Sherwin Huang. I recently sat down with Sherwin for a Q&A on what makes for great mobile design.

Sherwin Huang, Interaction Designer

Sherwin, briefly describe your role as an Interaction Designer.

In brief, I find creative solutions around technological boundaries, guiding and participating in production by balancing aesthetics with functionality to create a visual package that fosters user delight.

What do you think are the key issues in designing for Mobile Devices?

Uandme user experience

Applications – including the ones we create here at Locatrix – are increasingly feature packed and complex.  There is always the temptation to create user interfaces that display information equivalently to what one would find on an application designed for the desktop.  All this is done with the best of intentions thinking that it will allow users to have all the information at their fingertips.  But doing this on the mobile is sometimes akin to trying to squeeze an elephant through a door!

The mobile differs from the desktop in that often visits are purposeful. Users to go a site on their mobile because they know what they want (and there is a context to their requirements), whereas on the desktop users follow trails and search results to a site. So in designing for mobile you aim to fulfil this contextual need as quickly and easily as possible.

We often see different mobile applications that aspire to do similar things. How do you evaluate a “good” experience compared to a “great” one?

On the desktop, we can quantify this kind utility by looking at factors like learnability (how long it takes users to reach a given level of experience), clarity of structure (time taken to find a piece of information) and satisfaction from the overall experience. On the mobile this is even more important, because users are on the move. They are distracted, they need information quickly.  The equipment is often uncomfortable (small) and quite unforgiving (a slip of the thumb will take them out of the browser).

The most important questions to ask when designing for the mobile are: How will this be used? What will the users want in order to achieve their goal? How can we take the user to what they want in the shortest possible number of steps?

Answering these questions lets us produce an application with a goal in mind. The goal is to produce an application that a user can get into and use right away. Minimal learning curve. Minimal questions. Maximum results. That’s how we know we’ve got a great mobile experience!

Read more

A couple of months ago we were meeting with a product manager for a European mobile operator, who confessed he had a big problem with mobile social networking. His manager had done a “link deal” with one of the big social networks – you can probably guess which one – and with much fanfare, a new link and logo appeared on that operator’s mobile home page.

At first glance, this initiative had a tremendously successful outcome for the MNO. Their mobile Internet usage saw double-digit percentage growth overnight. And kept growing.

A week later, the operator announced increased usage caps for all of its data plans. No great problem here, as subscribers rapidly became new mobile social networking enthusiasts, often in their thousands each day. But certainly less revenue per MB.

In fact everyone was terribly pleased until later in the month they discovered that while overall mobile data was substantially up, their on-portal traffic had actually decreased, by more than 30 percent. And adding to that dilemma, ARPU decreased for nearly every VAS product they offered to their subscribers.

So while the social networking traffic was increasing, the mobile operator had become a dumb pipe – and found themselves dramatically exposed to churn in a competitive market. Because “m-site” social networking on network A is an identical experience on network B. And C. Or even D. Popular social networking sites are attracting millions of unique visitors to their mobile portals every month, and while mobile data usage rises, the ARPU curve – from data usage alone – is trending ever downwards. What should be an opportunity for mobile operators can very quickly become a massive problem.

To help mobile product and VAS managers meet this challenge, we devised the Locatrix (Re)Engage Workshops. Our thesis is this: mobile operators don’t need to “introduce” social networking services – their subscribers are already there. Instead, they need to formulate and execute strategies which provide a re-engagement path, via and through existing social networking services such as Facebook, Twitter and Friendster.

Delivered in either half-day and full-day seminar formats, our (Re)Engage Workshops help mobile product managers and network executives better understand the demographic mix of social networking users, and teaches them how to create a subscriber engagement strategy by working within the social networking paradigm. Creating, for example, a framework for injecting your mobile brand and VAS solutions into social networking portals, and helping your customers promote their favorite services to their friends. And while we of course present engagement examples based on Locatrix solutions and services, there is no ongoing commercial obligation from the (Re)Engage workshop – just an opportunity to learn and refresh your strategies for leveraging mobile social networking within your subscriber base. And (Re)Engaging with your customers!

There’s more information about the Locatrix (Re)Engage Workshops on our website, but for a limited time we are offering a free half-day (Re)Engage Workshop to qualifying operators who are readers of this newsletter: simply mention “Position Update” when you contact us, or use this special e-mail link.

Most developers writing web applications for mobile devices decide to:

• Develop for the most common devices.
• Develop so that it looks “kinda ok” on most devices.
• Use hacks to get it to work on a couple of other devices.
• Somehow use the WURFL database.

Several of our solutions revolve around displaying maps. We want the maps to fit to the width of each device. We also like to know what an acceptable base font size is. We want to know as much as we can about every device, so that our solutions work perfectly regardless of device. We run Salamander behind every major (and minor!) solution we develop here at Locatrix Communications to solve this.

Salamander lets developers write layout code for all devices at once. By allowing any service to get any attributes about any device. Mobile applications no longer have to look “kinda ok” on some devices. Applications become tailored to each device. For example:

• Display size
• Supported WAP version
• Supported Java version
• Official support by an MNO
• Default font size.

The web-based front end of Salamander also allows us to instantly change and/or rollback changes on any device-specific attributes across all our solutions. Additionally, it automagically pulls community updates from the WURFL database.

To call Salamander, we simply create a new Salamander object and then query the attributes we need.

if (!isset($_SESSION['device'])
{
    require_once('/include/Salamander.class.php');
    $salamander = new Salamander("http://salamander.me");
    $_SESSION['device'] = $salamander->getSalamanderDevice($_SERVER["HTTP_USER_AGENT"]);
}

The Salamander class handles all the communications with the Salamander server. It returns an array of various required attributes for applications to query.

We then query attributes such as:

• $_SESSION['device']['baseFontSize']
• $_SESSION['device']['imageType']
• $_SESSION['device']['imageWidth']
• $_SESSION['device']['imageHeight']
• $_SESSION['device']['is3G']

From there we resize images, set font sizes, enable/disable bandwidth intensive features, etc.

Want to try out Salamander with your applications? Want to send feedback? Send me an email!

You could say I’ve finally joined the current generation, but after more than a year of waiting on Telstra to release a 3G BlackBerry – and maintaining a vice-like grip on my old 7100x 2G device (no edge!) in the meantime – I’ve finally made the decision to upgrade to a BlackBerry Bold.

I have to confess, I was holding out a little longer, thinking that perhaps the Storm was the device to make all the Locatrix office iPhone huggers go “wow”.  Despite the fact that Telstra aren’t (yet?) releasing a Storm, an impending month of travel made me finally make the decision, and in doing so consolidate two SIM cards into one (my other handset of choice is/was a Nokia E51, which I still kind of like).
Read more