Fortunately, HTML5 is ready to answer the call. While the cross-platform markup language won't be finalised by the W3C until 2014 there are significant reasons to get the bandwagon now.
Making Web apps behave like client apps
HTML has long been the standard for building and deploying web content. Now it appears that this technology is on its way to being the standard for building and deploying apps as well. The newest iteration represents a shift towards client-side web development. Such a shift will benefit you for four reasons:
- Since HTML5 runs very well on all manner of devices, it offers cross-platform programming - which is huge for all of us overrun with BYOD requests.
- In addition, HTML5 was built with battery-powered tablets and smartphones in mind.
- Finally, HTML5 provides lighter, easier-to-read code than previous iterations.
Your mobile workforce and customers want to do everything they do on their desktop PCs on their smartphones and tablets-and HTML5 is the way to start manifesting that experience. With that in mind, let's take a look at eight HTML5 tips you should keep in mind as you build your websites and Web applications.
1. Video and audio integration
Flash is buggy, requires plug-ins, has frequent updates and gobbles up power on mobile devices. Steve Jobs let us know it, and Adobe rang the bell. Flash is going away on mobile devices-no more Embed or Object tags.
- Video: Used to render video content.
- Audio: Used to define sound content.
- Embed: Used to insert, or embed, some type of multimedia content.
- Track: Defines text tracks for video and audio tags.
- Canvas: Allows for rendering of games, graphs and other visual images on the fly.
Many web presentation elements have been made obsolete by Cascading Style Sheets, which stole their thunder long ago. While HTML5 will still render these items, you really should have shifted away from them years ago. If frame elements are no more in the HTML5 spec, though, then what we are left with to replace them?
Enter HTML5 semantics, which are carefully designed to extend the current capabilities of HTML while still enabling users of legacy browsers to access your content. These shouldn't be thought of as simply features you may or may not use, but, rather, the foundations upon which you build web apps and pages. These semantic elements enhance the user experience and touch several areas, including search, accessibility, interoperability and internationalisation.
It doesn't take a genius to figure out how, or why, these are important changes. A correctly coded page should have page title and posting info in its Header tag, with the article body falling inside Article tags. Items such as social buttons or follow-up items appear in the footer. Put another way-no more search algorithms or guesswork in determining what type of content goes where. The end result is simply a better user experience.
3. Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)
Currently certain portions of your site remain unavailable to people with disabilities, including the blind and those people unable to use a mouse. HTML5 tackles this problem by defining functionality to be used with current assistive technology.
W3C's WAI-ARIA provides a framework for adding attribute identifiers or roles to the different elements of your HTML code. Some of these roles will be built-in, and web authors will not be able to override them. These identifiers mark common regions on the page - such as Title, Header, Footer and Nav - and provide a more effective way to present your information to a wider audience than their predecessor, the tag.
Let's take a closer look at what this technical spec brings to the table:
- Role types for widgets, including TreeItem, Menu Slider and ProgressMaster.
- Properties that define a widget's state.
- Properties that define the more active regions of a web page.
- Drag-and-drop functionality properties that also describe targets.
- Better keyboard navigation
Meanwhile, additional HTML5 page structure elements include the following:
- Section: Used for article or subject differentiation or to separate different parts of an article.
- Article: Defines the body of an article.
- Aside: Defines content that is relevant, but not central, to the flow of an article.
- Time: Lets users define time values in both human- and machine-readable formats.
- Menu: Typically used for context menu building, this represents a list of commands.
- Hgroup: Wraps multiple headings in one place.
- Figure: Creates a figure as a single item. Normally, this would be an image or group of images.
- Figcaption: Hold a caption for a figure.
- Cite: Represents the title of a piece of content, whether it's a book, article or essay.
- Progress: Represents how much progress has been made on a particular task.
- Details: Creates accordion-like effects that are activated when clicked.
Remember when Ajax and Web 2.0 were all the rage? Well, here comes WebSockets. This inclusion allows developers to talk to the server without multiple Ajax requests, thanks to PUSH technology.
While WebSockets is still in the W3C's standardisation process, several browsers, including Chrome and Safari, already support it.
5. Web Storage
Who wouldn't want to mimic the client application experience within the browser? Web Storage is a big part of W3C's plan to do just that. Web Storage can be thought of as a more advanced cookie or client-side database. It has a much higher storage capacity than your average cookie, up to 10 MB, and it is stored on the client side.
There are two types of Web Storage: session and local. The Local Storage API makes apps possible without third party plug-ins. It consists of key value pairs that can be stored and retrieved from your browser, go right to the hard disk and are stored indefinitely. It's very similar to a client-side database, in the sense that it can't be deleted or cleared. In fact, data will be stored even after the browser is closed.
Session data, on the other hand, is stored in the Http session and is tied to the life of the session. When you close the browser, the data is gone.
Both types of Web Storage use the same basic API and are supported by most current browsers. Together, they make several web application features easy to pull off, including storing user information, caching data and loading the user's previous application state.
6. Geolocation API, or Web-GL
Previously, geolocation apps were native to particular devices. Here's where HTML5 comes into play, as it brings with it the ability to include geolocation capabilities in most web applications. Data sources can include GPS, GSM/CDMA Cellular IDs, IP addresses, Wi-Fi, Bluetooth, Mac addresses and old-fashioned user input.
The Geolocation API can add necessary filtering to your search queries. Whether a user is on a mobile or desktop device, the Internet will know where the user is and display relevant, location-based results. It isn't perfect, as there are occasional errors, but geolocation technology will only get better with time - and the applications for this API are endless.
7. Cleaner code
Coming from a development background, I can tell you that the average developer is very passionate about clean, simple code. Code should be short, concise and as descriptive as possible. HTML5's clear, semantic and descriptive code separates style and content very easily, which makes code cleaner and easier to digest.
It's also worth mentioning the simplified doctype. Not a big deal, you may say. True enough, but I'm a fan of cleaner code, and I love the fact that I no longer need to use a long, unintelligible piece of code filled with different doctype attributes.
< !DOCTYPE html >
That says it all. Furthermore, sites that rely heavily on Flash today will see SEO improvements tomorrow, as their cleaner code is made more digestible to search crawlers.
8. Better website interaction
A good website lets users interact, not just stare and read. With the Canvas tag, you can create interactive and animated creations that had been previously relegated to Flash. That, along with HTML5's ability to recognise common tablet gestures like swipes and pinching to zoom, sounds a lot more interactive to me - and even lets you create mobile-friendly games
HTML5 helps you "build once, run anywhere"
HTML5 seems like the straightest distance between two points and, therefore, the easiest way to improve customer experience in the mobile world. If you build to its standards, you can ensure a great mobile user experience with the newest devices while making sure that older devices aren't denied your content.
"Build once, run anywhere" is the main reason I choose to develop with HTML5. No more designing three apps for three different platforms. If you're worried that some browsers aren't supporting these features, you can still be using these elements with one of the many libraries and scripts available, including Remy's Shiv or Modernizr.
Companies and brands that utilise this technology will have the necessary tools to create positive brand awareness via rich web content within an app-like experience. This, in turn, will increase traffic and conversions.
At the end of the day, with the mobile market revolution growing at a staggering pace and no sign of slowing down, the question is simple: Why not embrace HTML5?