The HTML5 date element is an especially great addition in the mobile world. It triggers native controls, built for mobile devices, instead of forcing the developer to come up with a normally-complex solution. Support was not there for a while but apparently things are improving as of late.
For example:
iOS 5.1 Safari
Android 4.x Chrome:
But sadly, the native Android 4.x browser is not compatible.
I say, use it!
Say what you will, this is pretty cool – at least at the idea level: a specialized, HTML5 web browser for mobile devices that provides special hooks for HTML5 apps granting them access to native device features. Pretty nifty, right? Naturally the people who control the platform, kinda get to decide what can and cannot run, maybe get a cut of the action for the business that they are generating for you and for the work that they invested in making and marketing the app.
In exchange for openness, you get cool features (especially for games) and capabilities you otherwise will not be able to provide. Tradeoffs tradeoffs. Still, pretty darn cool.
Recently, a client asked me and my colleagues for a point of view on whether they should develop a profoundly animated website in Flash or go with HTML5. I love HTML5. I worked in Flash in the bad old days and was not a fan. I love HTML5. I even have the sticker on my laptop.
This is naturally prep for a big but.
It comes in the form of the list we shared with our client.
Look at it as a conversation starter. Be nice.
This list is VERY MUCH for the present time. Things change fast and HTML5 is gaining a foothold faster than Flash is losing it.
Still, right now, it's what I believe. Flash had to be the way to go. Sounds apologetic, no?
OH – and we ARE building an HTML5 mobile + tablet version of the same site. Mobile web vs. native apps – now that's a holy war I do take sides on.
