Rich (@rmanalan) pointed me to a post called Why Mobile Apps Will Soon Be Dead.
This is, and has been, a hot topic for quite some time, as developers move to mobile and are faced with learning new skills on new platforms and face new deployment and distribution hurdles.
From what I’ve heard, it functions just as you’ve come to expect from the native versions.
This is huge.
We took in a session last week called “HTML5 Wow” presented by two Google developers that showcased the file, graphics and audio features of HTML5. You should check out the slides, which also implement many HTML5 features, most notably animations.
One caveat, your browser might not be able to render it in all its glory. Try using the Chrome Canary build, which you can run side-by-side with your existing Chrome build. If you’re not using Chrome, why?
You’ll also need to enable the Web Audio API to hear sound.
By now, you’ll see one big issue with building for HTML5, inconsistent browser support for it. Even so, browsers are catching up quickly, both desktop and mobile, and by this time next year, mobile web development will be even more attractive.
But will it be too late?
Jason Grigsby (@grigs) brings up an excellent point about the web vs. native argument in his Links Don’t Open Apps post:
Are you having trouble convincing people that they need to develop a mobile web site as part of their overall mobile strategy?
I have a solution for you. Ask the people you need to convince if they do any of the following:
- Send email to their customers?
- Participate in social media?
- Search engine optimization?
- Advertise online?
Each one of those marketing efforts is based on links. And links don’t open apps.
Although I love the open web, I’m inclined to think that it won’t seriously challenge native development until 2013.
Why 2013? This year and next will be spent evangelizing and advancing HTML5, both its spec and the browsers that support it. Early development success stories will rise, and by 2012, large development shops will begin to switch.
The enterprise may actually drive HTML5 innovation, since the costs associated with native development are higher for them, mostly due to sunk costs in IT, existing skill sets, and the rise of rich web apps and devices like Chromebooks.
Obviously, all opinion, but that’s why we blog, right?
Find the comments to share your thoughts.