The Role of User-Experience Design in RIAs

Walking home the other day I ran into an old high school classmate who I hadn’t seen in over 12 years. We did the obligatory catching up, and of course she asked what I did for work. What followed was a typical scenario. I explained I was a user-experience consultant for Adobe, which was followed by a blank stare.

“You know, Flash” … Another blank stare.

The fact of the matter is a lot of very bright people use our technology every day, whether it be Flash Video, Flash Applications, PDF, or consume a product that has been designed by Adobe technology, and have no idea that they are using Adobe technology.


In that light, I’ve found that the recent conversations back-and-forth about Silverlight and Flex/Flash have been almost exclusively developer-focused … a sort of, “lets stack our tech-specs and stats up against yours”… and what seems to be getting lost in the conversation is the “User”. The point of this post is not to go down the whole Silverlight / Flash road, but I will say that most, if not all of your users will have no idea whether your app was built in Flex, Silverlight, or AJAX, or event know what those words mean. They will have an experience with your application, and if its a bad experience, regardless of how great the technology is, they won’t come back.

One of the great things about working for Adobe, and with Adobe Technology is that Adobe has a decades-long history when it comes to user-experience design, and been at the forefront of helping to define good user experiences, and enabling others to define great user experiences. However, and this may sound like heresy as an Adobe employee, Adobe does not have a monopoly on user-experience design. Adobe doesn’t “own” user-experience. User experience belongs to the user.

Another great experience that I’ve had working in Flex with some of the best and brightest Flex developers is that I have never designed anything that our developers couldn’t build, and I’ve designed some pretty wild stuff. The response we always get is, “we can build anything, some things just take longer than others”. I love the freedom that I get to design and focus on the user, and not be constrained by the technology.

So, my point of this post is the following.

If you’re going to build a rich internet application, whatever technology you use, do the following:

Hire a great User Experience designer: Flex makes it easier to develop great experiences, but you still need designer to determine what the most appropriate experience is.

Give designer and developer opinions equal weight: Consider the role of the designer as on par with your developer. Developers need designers, and designers need developers.

UX Design is about usability AND polish: Users’ connections to an experience is more than just how easy it was to complete a task. It’s also about an emotional connection. It’s about how fun the experience was, and how visually engaging it was.

Give designers the freedom to go beyond out-of-the-box: Flex includes a good set of out-of-the-box components that make it easy to develop applications. However, don’t limit your designers to that component set. Let them explore and find the best solution possible. And then evaluate how expensive it would be to implement that solution against the user needs.

Here’s to great user experiences.

5 Responses to The Role of User-Experience Design in RIAs

  1. Ben Dalton says:

    Great post.

    I think you’ve really hit the nail on the head here. Too often, we forget to take into account the way all of the ‘little things’ add up in terms of user experience. It is much harder to elicit one ‘wow’ from a user than to prevent complaints.

    In addition to the overall user experience, when a UX designer thinks outside the box, they sometimes come up with ideas that are outside the realm of normal requests for a developer. These extra-ordinary ideas can push the boundaries of what we do with our applications. Additions that are outside the norm can inspire others and contribute to the entire development community. The more we push ourselves and each other, the more the users benefit.

  2. I concur, great post. Anyway, I’d even take it a bit further in saying that most flash designers/developers REALLY get UX design. Especially considering all the heat we’ve taken from the usability groups over the years. Its blatantly obvious when you see most ajax developers repeating the same mistakes nowadays.

  3. Sid B. Dane says:

    I totally agree! Some people might think that using a Rich Internet Platform like Flex ensures Usability and a great User Experience, but that certainly isn’t true.

    Developing ANY application should always be about a) the business needs b) the technology possibilities an capabilities and c) the user needs.

    The three should be in balance. And then, from a technology point of view, a good platform like Flex enables technology do use better standards, develop quicker and have more capabilities within a project’s budget. And if the technology is better capable of doing that, the business needs as well as the user (experience) needs are better met.

    S!d

  4. Nice, thoughtful post and wise counsel. I’d also add that people sometimes forget that even when they build applications without a designer that they are still in fact are ‘designing’ something. In fact, one of my favorite quotes is from designer Doug Martin.

    “Questions about whether design is necessary or affordable are quite beside the point: design is inevitable.

    The alternative to good design is bad design, not no design at all.”

    Cheers.

    Chris Bernard
    User Experience Evangelist, Microsoft.

  5. Anilkumar.K.A says:

    “Give designer and developer opinions equal weight”

    The above line.. It really strikes, because when a designers puts in some suggestions, the suggestions gets washed away as the developer comes with a techincal word which makes a designer to cover his ideas and end user is no where concerned.