Adobe’s decision to cease development of the mobile Flash platform and increase their investment in HTML5-related efforts created perhaps the final piece of conclusive evidence that HTML5 is the current go-to technology for creating ubiquitous user experiences regardless of device.

While there’s been an abundant amount of discussion on what this means to developers, there’s been a lack of focus on what this means to the overall user experience (UX). If HTML5 thrives where Flash struggled and becomesthe dominator in the choice for new mobile and desktop technology, will users benefit from the transition? Yes, as long as designers and developers do their jobs right.

Different stroke for different folks

Apples and oranges. The question is, which one’s Flash?

It might seem strange to compare Flash and HTML5 at all, since they are so inherently different. Whereas Flash is proprietary, HTML5 is continually developing through open source collaboration. If Flash is a seasoned monarchy, then HTML5 is the wild wild west. It’s important to note that there are tons of applications and sites in which Flash and native apps will remain the preferred choice of implementation. However, that doesn’t mean that we can’t explore the major differences between the two in order to discuss the gaps that HTML5 can fill where Flash is lacking.

Flash, by nature, is a control freak. It demands browsers have the latest plugin, or it will be sure to let you know if it’s unhappy with your version – perhaps even go on strike until you upgrade. It thrives on presenting a consistent, desktop-centric experience of typefaces and layout, and never bothers to worry about changing the user experience based on device nor the context of what you might want to do on that device. But Flash has had years to evolve from the land of bouncy ball demos and splash screens to the product for creating some fantastically innovative interfaces.

By contrast, HTML5 excels at giving users a delightfully inconsistent experience on any device through the concepts of “graceful degradation” and “progressive enhancement.” Both concepts are designed to provide users the best possible experience each browser allows for, whether a content area displays a static image in Internet Explorer 6, or a fully functional HTML5 video in Chrome. Since desktop browser usage runs the entire spectrum of worst- to best-case scenarios, this way of designing user experiences can help ensure that all users get the most bang for their buck out of their browsers. Gone are the days of being forced into creating identical experiences based on the best performance of the worst browser.

Those who advocate web standards also support the important role HTML5 plays in responsive web design, or the systematic display of content, tasks, and layout, depending on whether the user is viewing the site on a mobile or desktop-sized browser. The reasons why people view the same website on a mobile device versus a desktop is often very different. For example, a user viewing a site for a restaurant while sitting at their office desk could likely want to view a workflow more supportive of exploring the menu, reviews and other content that would help decide if it’s a good place to eat. On the other hand, a user viewing the site from the passenger seat of a car might want to quickly find content based on the assumption that they have already decided to eat there, such as directions or the phone number.