The Mobile Spoon - Gil Bouhnick's Mobility Blog
Home My Favorites iOS Apps Talk To Me About

Nov 28, 2012

Is HTML5 Truly Ready For Prime Time?

HTML5

Some say 2011 was the year of the big breakthrough for HTML5.
From a promise to something real. A technology supported by a growing number of developers. The only true device agnostic alternative.
Well, if 2011 was the year of the big leap forward, seems like 2012 was the year of the disillusionment.
HTML5 became one of the biggest topics for debates, being mostly smacked down by many experts.

Gartner recently stated that HTML5 is still 5 to 10 years from becoming a suitable basis for businesses.

I think they are wrong.

I am certain it will happen much faster. For many businesses it is already happening right now.

Many people have mistakenly defined HTML5 as an equivalent alternative for native development. It cannot be, just like a web based email client such as Gmail cannot compete with a native rich client such as Outlook.

And yet, organizations are successfully using web-based tools for doing business, isn’t it?
Windows is undisputedly dominant in the enterprise, and yet most software vendors build web-based products and stay away from native technologies, aren’t they?
Web tools are part of any IT strategy and only 10 years ago experts claimed that web applications will never be able to replace native products (I remember I used to protect native technologies such as MFC and .Net against those wild, disordered web developers who used plain text editors with no compilers… they’ve won. I lost. I’m now part of their team).

The same will happen in mobility, and it will be thanks to HTML5 and other mobile-web technologies.

Yes, Mark Zuckerberg wanted a kick-ass mobile app for facebook and couldn’t get it using HTML5, but to be honest, facebook’s desktop version isn’t exactly the top of the art in terms of user experience either, so maybe it’s not all about the technology after all?


gartner_hype_cycle_html5_top

So 2012 seems like the year of disillusionment for many HTML5 developers, but it’s not because it’s a bad technology. It’s because it’s so good it managed to dazzle all of us.

Think about it for a second: a new technology which is not even close to being standardized, already responsible for the death of a few other successful technologies, already supported by all the leading platforms, being used by a huge number of organizations, products, platforms, and more.
That was the peak of inflated expectations, and from there it could only go down.

So during 2012 people and organizations have learned that in some cases (or better say: some Android devices) the user experience provided by HTML5 is not yet perfect. Developers have learned that in some areas there are still functional gaps. The world has learned that HTML5 will never be a good fit for developing games. It learned that HTML5 does have limitations.

It changes nothing, because what the business world has also learned is that HTML5 brings a perfect answer to many of its’ needs: it’s easy to deploy, flexible and configurable beyond any imagination, truly device agnostic, beyond just mobile devices, and most of all: can support the majority of the business needs fairly easily (and also interact with complementary technologies to close some remaining gaps if exist). 


My personal experience with HTML5:

I’ve been involved with mobile development for the past 8 years. Java, Embedded C++, .Net, WAP, Objective C, Windows Mobile, CE, resistive screens, styluses, you name it.

We started using HTML5 back in 2009, when it was fairly new and not as popular as it is today.
Back then, we were asked to build a native BlackBerry client for a few of our clients. Java for BlackBerry was the obvious way, but we felt it would be a matter of time before iOS and Android will become popular among our enterprise customers. We wanted to develop once and still support those new platforms. We made a bet on HTML5.

Today, old BlackBerry is dead, and BlackBerry 10 is just around the corner. It will have a solid support for HTML5, just like iOS and Android have. We made the right decision.

ClickConnect on Devices2

So back to 2012: while people were debating whether HTML5 can compete with native or not, we at ClickSoftware, spent our time deploying our mobile solutions among many of our large enterprise customers all over the world.
Thousands of mobile employees are using our HTML5-based products today. They love it. They run it everywhere, on multiple devices from smartphones to tablets, including laptops and desktops. Some are using our products as pure web-based apps, while others have selected to embed it inside native containers. Functionality wise it gives them exactly what they need, with the ease of web-deployment, brilliant configurability and extremely high flexibility. Using Responsive design, our solutions not only run everywhere, they are adapting to the device type, screen size, peripheral devices and network availability.


2013 is right around the corner, and I’m sure we will see more products designed to run everywhere using HTML5.
Few years ago I predicted that by 2013, HTML5 will rule enterprise mobility. In some aspect this prediction has already materialized. In other aspects it will take longer, as companies are still learning the pros and cons of the mobile web, and with time will learn how and where to make a better use of it.



13 comments:

Anonymous said...

I agree with most of it.
Facebook mobile app is bad but it's not because it's using web, it's because it's simply bad.
LinkedIn mobile app is the right example for what can be achieved using HTML5.

Rashid N. Khan said...

HTML5 is an excellent solution for a large number of applications, and every day the number of such application increases as more and more capabilities are added to HTML5. However it is not good for everything, and no one should expect it to be good for everything. Like any other development language the developer must decide if it is good for a particular application or not. There is no magic bullet. And the fact that HTML5 does not d everything for everybody does not make it bad! So one must have the right expectations..

I also believe that FB failed with HTML5 not because of the limitations of the latter but of the former. My guess is that FB probably did not have a good strategy and rushed in to the development because of intense market pressure.

So we at Chatty Solutions (www.chattysolutions.com ) use HTML5 for all our client-side apps. Yes we can not bid for 20% of the apps out there where native functionality is a must, but the fact of the matter is that the remaining 80% where HTML5 works great is a HUGE opportunity. So, regardless of what FB does, we are sticking with HTML5!

Rashid Khan
rashid@chattysolutions.com

chnlove scam said...

So nice to be here and see your post! Appreciate!

help with dissertation said...

This blog post Is HTML5 Truly Ready For Prime Time provides the light in which we can observe the truth, It will for all time be inspiring to read content from other writers and apply a little something from their store,

Android App Development said...

Yess HTML 5 is the best language of web.

BARTHOLO MEW said...

You posted editorial Is HTML5 Truly Ready For Prime Time? which gives users bunch of information concerning meticulous subject recognition for this allocate.
dissertationproposal.info

iPhone App Development said...

I completely agree HTML 5 is one of the best and most used language of web.

Android news said...

HTML5 is the format that will conquer all the others. And it will happen very soon.

accounting dissertation topics said...

Appropriate a great way of Being Introduced to this topic Is HTML5 Truly Ready For Prime Time? material. It was great catching up is this? be grateful you gently for the conclusion,

Annie@webgarage.in said...

I think yes, HTML 5 is the best language till now.

3D Animation Studio said...

I don't t know how should I give you thanks!

Akhilesh Gupta said...

Well, HTML5 has brought a set of goodies that makes it suitable for embedded / mobile apps, in addition to web based apps! However I understand that fragmentation is the major issue in HTML5 adoption - which is like not a uniform support on HTML5 features. A HTML5 app will rely upon underlying browser/rendering engine for its execution! What's your opinion on this? Also that how do you address that when you rely upon the in-build rendering engine of mobile phones?

Nishanth said...

Cool.Good stuff.

HTML5 Training
Online JavaScript Training
Online HTML5 Training

Post a Comment