Oracle UX User Experience

Oracle’s user experience team is building enterprise cloud applications for the way humans move through their day. That means much more than designing for mobile devices first. The UX we create needs to let our customers’ users shift between their personal and professional devices and lives more easily.

As such, our enterprise mobile strategy includes:

  •  A consistent UX across devices so that everything looks the same and users need to learn it only once.
  •  Common, core components, based on UX design patterns and built with Oracle technology, tailored to each device (for example, a mobile shell for a smartphone).
  • Simple, task-based access to each application.
  • Smart UX features that can capture input data and generate context to anticipate user needs.
  • Designs that accommodate quick, one-handed “coffee-shop interactions,” letting users move from intent to action quickly.

All of the same data that users expect to have on their office desktops is still on their mobile devices, but we’ve refined the workflow to include only what is mandatory for tasks they might do on their smartphones.

Thin Is In

We’ve built a mobile shell with navigation that mimics the desktop application, notifications that let users deal with the things that require their immediate attention, and controls fine-tuned for a quick swipe of the thumb.

The result is a simplified mobile UX, with just the essential, task-based options users need to do their work, whether they’re in between meetings or juggling life along the way.

These tasks that are surfaced to users’ mobile devices are slimmed-down versions of desktop workflows. We’ve covered all of the basics and then built in the ability to add on whatever else the user thinks is essential.

We’re focused on coffee-shop interactions—quick actions a user might take with a phone in one hand and a cup of coffee in another—because that’s what our research tells us is important. These interactions might be approval of a report or a skim through notifications to make sure the user hasn’t missed anything important. Whatever a user needs to check on is moved to the surface. It’s the UX team’s job to know what that is, even when the user doesn’t, and make sure it happens.

The goal: Let users interact with the system quickly and easily, taking the shortest path from intent to action. This gets back to what we call a “thinness of experience”—the system knows what you’re going to do, and how that can be done best.

We’re streamlining the mental load most humans carry—how to input and find needed information—so that they can make decisions in a timely fashion.

Leave a Reply