Just back from speaking about cross-platform design patterns at the Oracle Applications User Experience (Applications-UX) training event in Munich, Germany (March 6 and 7, 2012). The Oracle EMEA sales audience (yes, the UX Samba is worldwide) heard all about how Applications-UX research and design expertise created these building blocks for a new standard in enterprise applications user experience, how they are used by Oracle's developers, and what they mean for Oracle applications users, customers, and partners too.
What Are Design Patterns?
Design patterns are reusable user experience solutions to common problems or tasks in enterprise software. Using design patterns means our internal developers have proven, easy-to-follow design guidance implemented with Oracle Application Development Framework (ADF) and Fusion Middleware (FMW) components. The development process can scale, and the result is highly usable and consistent user experiences in our apps.
We can also make those patterns available to customers and partners who take Oracle applications usability even further by creating new usable solutions when they tailor our apps. Check out these Oracle Business Intelligence Enterprise Edition 10g and 11g design patterns, for example.
Design Patterns Explained
When speaking to non-UX audiences, it’s important to grab their attention early, speak in plain language, and use examples that they can relate to. In the case of design patterns, I could have told them about Christopher Alexander and A Pattern Language: Towns, Buildings, Construction (1977) and how design patterns became popular in software and web development. But they might not remember that or know how to apply it!
A sales audience wants to know about a competitive message about how design patterns help apps users navigate a virtual world easily, and how this knowledge can be used by to develop and extend usable apps. Using everyday examples that we are all familiar with, and adding in local flavors, gets the message across.
Searching for and adding items to Amazon shopping cart before signing in.
Using a DBahn date picker to automatically selects a date in the right format.
Typing add in Google Maps is faster that selecting options from a list of values or waiting for search results.
So, to help illustrate, I used the “lazy registration” (that is, you can do your shopping and sign in or create an account later) on Amazon.de, the date picker on the Deutsche Bahn web site, the typeahead feature in Google Maps destination search, and a few other well-worn patterns that we now use on the web without even thinking!
Looking forward to the next opportunity to tell the Applications-UX design pattern story and to finding local examples that work for the audience too.