Tuesday Apr 02, 2013

UX Design Pattern Spotting with Fusion Mobile Expenses

One of the great things about demoing cool stuff for Oracle Applications User Experience is that you're entering a world of discovery of guess what? Even more cool stuff! I was showing off the Fusion Mobile Expenses app live recently and explaining how our UX Design Patterns make for developer productivity and satisfied users. A developer hand shot up in the audience and asked me to point out which patterns were being invoked as I stepped though the mobile tasks. What a super question and a great demo value-add to include in future!

Fusion Mobile Expenses video on the Usable Apps YouTube channel

You can see the patterns at work easily. Look at the rockin' Fusion Mobile Expenses video, for example, and within one minute you can see a bunch of the publicly available Mobile UX Design Patterns in action. There you have the Springboard Navigation pattern (that screen at about 19 seconds in), the Page Header and the Input Form patterns (at about 40 seconds), and so on.

Shown live, the Fusion Expenses mobile app reveals even more patterns, such as the List pattern, my favorite the Actions pattern, and others.

List and Actions Pattern

List and Actions patterns in use together in Fusion Mobile Expenses.

So, come along to my next UX outing on building great mobile apps with Oracle Applications User Experience reusable design solutions and see the patterns used and explained in context. Don't miss this opportunity by staying tuned to the events and outreach page on the Usable Apps website. I might even start giving out prizes to the audience if you can name the patterns when they come to life in the apps shown!

If you want to read more about using design patterns for mobile apps in business, then head on over to the Vennster blog.

Altogether now: "Taxi! 25 Dollars!

Friday Mar 09, 2012

Oracle Applications User Experience Mobile Apps Design Patterns

While in Munich, I also talked about the Oracle Applications User Experience (Applications-UX) Mobile UX strategy.

The Oracle Applications-UX team has made a strategic investment in mobile user experience, with a dedicated team of cognitive psychologists; usability engineers, interaction designers, architects, and so on that innovates fast and hard, brainstorms on cutting edge mobile UX design solutions for all Oracle applications. The mobile space changes rapidly, and this presentation generated a lot of excitement and energy in the audience.

Again, I used local examples to get the message across. I used the Android version of the clever-tanken.de app as a local market example (on the day the top paid Android app in Germany) and illustrated how important ethnography is to the user-centered design process behind our mobile strategy.

Finding that cheap gas in Germany with the clever-tanken.de Android app.

For example, although almost 90% of German workers are contactable out of hours, workers don’t always want to be reached and value their work-lfe balance. VW has agreed not to contact workers in six plants in Germany on their BlackBerries out of hours accordingly. So, from a user requirements perspective in Germany it’s critical to take into account those labor unions or Betriebsräten as stakeholders.

I also explained our user-centered, multistakeholder, mobile design patterns creation process (it includes Apple consultation in the case of iPhone app designs), and how these patterns provide proven cutting edge user experience solutions in a scalable, reusable way for mobile app development teams.

Developing apps using these up-to-the-minute olutions requires a development environment to match. The ever-changing mobile O/S landscape, ADF Mobile enables developers and partners to respond rapidly to changing user experience expectations without redeveloping content. We can support the same content, easily, across different devices with no compromise on user experience or native O/S navigation or actions, while addressing mobile data security issues that customers tell us about, and more. Read the Oracle ADF Mobile white paper for more details.

If you’re presenting to worldwide audiences about mobile user experience, then I recommend that you check out appannie.com for the latest market intelligence including local app popularity charts (it's iPhone, iPad and Android right now) and some very nice infographics on the state of mobile computing. Other useful stats on mobile usage growth, including number of devices and data usage, is available from techcrunch.com.

Friday Apr 22, 2011

Geezers and iPhones

Shortly after I relocated to the United States I realized that the term "geezer" wasn't a reference to one of those dodgy, fast-talking, wheeler-dealer character types from "Eastenders" or "Only Fools and Horses", but to an, eh, more mature person. All sorts of labels apply to the older generations: seniors, senior citizens, old folks, the elderly, old age pensioners, and so on. From a design perspective though, whatever you call this group of users, one thing is clear: the last thing you want is a UX that screams "older user", something I was reminded of by this Irish Times article.

Nowhere is this clearer than in the smart phone space. Instead of offering older users dumbed-down and patronizing designs with over-simplified features and larger controls, it is possible to offer a graceful, highly intuitive and classy design for all. The iPhone for example is one such device that works for users of all ages simply because of a great universal design, and one whose form factors--the large display and controls--work especially well for older users (though perhaps some of the finger-based gestures not so, maybe). Compare the keyboard experience when sending an SMS message on the BlackBerry with the iPhone, for example.


The Nokia 6310 phone was another device example, cited by the article, that was very popular with older users, yet like the iPhone was never marketed specifically for that age group (mind you, an endorsement by Jeremy Clarkson of any product would be enough to put me off it for life).


These older users must not be forgotten from design perspective. They're active with technology and online too, and besides the obvious social inclusion aspects of universal design, to not consider their UX needs leaves designers missing out on a very large global audience, one with a lot of economic clout. And, of course, we're all getting older too. If we consider ageing as an accessibility issue, then remember we're all "temporarily abled" up to some point in time, so designing for age is a wise investment, one that doesn't mean compromising on features or usability in any way (in fact, designing on accessibility ground has often led to improvements for the entire community). For details of the importance of this group in Ireland as well as some general observations, see the proceedings of the Business of Ageing conference.

So, it's not just "UX for kids"  that we need to think about.

Addendum: I picked up some great Tweets on this subject from CHI 2011, triggered by Alan Newell's presentation: Older people - a commercial imperative.

@chatchavan: #chi2011 Alan Newell: older people don't want "accessiblity". They just want to use the damn system!

I must read that paper!

Thursday Sep 30, 2010

No More Fart Apps. Would We Ever?

I loved Lucy Kellaway's (she of the Financial Times) article "Words to describe the glory of Apple" comparing the language style used by Apple and Microsoft and wondering if language style impacts the bottom line. If you don't want to register for the article, then the podcast version is here.

iFart Screen

Ms Kellaway tells us that Apple's language makes for content that is "fun to read", "elegant", and "makes you laugh". It has a tone that is "direct', 'comic", and "elegantly threatening". She contrasts this with the Microsoft language used for the new version of Internet Explorer, "architected to run HTML5, the beta enables developers to utililize standardized markup language across multiple browsers" and the rest. This is "standard stuff" from Microsoft, and Luce is "irritated", "bored", "alienated", and "restless" with it.

Actually, I think the article is unfair to Microsoft, who do care about language and the example used is not representative of language used in other Microsoft products - games, for example. Plus, the audience for their words is different to Apple's; basically it's a marketing pitch to Microsoft's partners, encouraging uptake of a beta release.

The Apple language that Ms Kellaway admires is taken from the App Store Review Guidelines (full PDF version); a set of guidelines more likely to be read by geek and hobbyist developers working from home than the corporate equivalents. Such language is not used in other Apple products themselves. In fact, language quality is not an acceptance criterion for App Store submissions at all. That of course, is telling in itself. Why not let the market, the users, decide on the language? In line with this, the Human Interface Guidelines from Apple for the iPhone has a common sense approach to language style. For example:

In all your text-based communication with users, be sure to use user-centric terminology; in particular, avoid technical jargon in the user interface. Use what you know about your users to determine whether the words and phrases you plan to use are appropriate.

For example, the Wi-Fi Networks preferences screen uses clear, nontechnical language to describe how the device connects to networks. Very reasonable from a user experience perspective. But, then Lucy says: "You might think there was a clear commercial advantage to be had in writing clearly and stylishly. But you would be wrong."

Not quite. There is a relationship, though it may not be all that visible to key decision-makers. That's because the commercial advantage does not come from writing clearly or stylishly per se, but its application. It comes from writing content that users actually want, in a way that they can understand, using terms and language that suits them; and that facilitates easy search and retrieval. The result is a quicker transfer and comprehension of information leading to better productivity for users and less training and support costs. And that's a competitive advantage.

In the enterprise applications space the opportunities for a product language tone that is "fun", "comic", or "elegantly threatening" doesn't exist in the same way it does for the iPhone app development community (and let's face it - for all the BS about the iPhone - most apps are little better than free low-tech toys designed by rank amateurs).

But that's not the point. The point is the language should suit the audience for the information. We need to spend less time worrying about our internal language style and all its nuances and rules and concentrate more on how users - our customers - themselves want it to be, and actually use it. Bringing terminology in line with user expectations and concentrating on a few basic writing principles grounded in research on information search, retrieval, consumption, and problem-solving would yield far better bottom line results than fretting about a rigorous adherence to every single aspect of a style guide for no other reason than it's there.

Tuesday Apr 13, 2010

iPad and User Assistance

What possibilities does the iPad over for user assistance in the enterprise space? We will research the possibilities but I can see a number of possibilities already for remote workers who need access to trouble-shooting information on-site, implementers who need reference information and diagrams, business analysts or technical users accessing reports and dashboards for metrics or issues, functional users who need org charts and other data visualizations, and so on. It could also open up more possibilities for collaborative problem solving.

User assistance content can take advantage of the device's superb display, graphics capability, connectivity, and long battery life. The possibility of opening up more innovative user assistance (UA) solutions (such as the opportunities afforded by the natural UI or maximizing graphical UA possibilities like comics) is an exciting one for everyone in the UX space. Aligned to this possibility we need to research how users would use the device as they work.

Thursday Nov 26, 2009

What Do Users Want as User Assistance on Mobile Devices?

One of the great things about my job working on the user experience user assistance team is I get to do research all aspects of user assistance on all kinds of platforms and devices. This is serious research, but it's fun too!

I love working with mobile devices, and already have too many to play with at home too. Recently, myself and my coworker Rhonda Nelson conducted a focus group with some users of business apps on mobile devices to find out what alerts, messages or help they wanted while working. From our research, empirical observation (and own experiences) we figured that the possibilities offered by native device capabilities might be mentioned (consider, for example, how users of GPS-capable devices like the Android HTC or Apple iPhone might use Google Maps to "help" them locate or transit), but would this expectation be borne out by the focus group? What else would be revealed by the users?

Well, you can find out by reading the usableapps blog article "Researching What Users Want from Help and Alerts on a Mobile Device". We will continue research into user assistance on mobile devices, including the use of e-readers like the Kindle or Nook - really looking forward to some interesting UX research with our users!


Oracle Apps Cloud UX assistance. UX and development outreach of all sorts to the apps dev community, helping them to design and deliver usable apps using PaaS4SaaS.


Ultan Ó Broin. Senior Director, Oracle Applications User Experience, Oracle EMEA. Twitter: @ultan

See my other Oracle blog on product globalization too: Not Lost in Translation

Interests: User experience (UX), PaaS, SaaS, design patterns, tailoring, Cloud, dev productivity, language quality, mobile apps, Oracle FMW, and a lot more.


« July 2016