At the company I work for, Virtusa, we often encounter scenarios where a client has an existing WCM or other web-enabled solution that they want to expose to mobile devices. In these cases, it is not enough to just point your mobile browser to an existing URL and have at it. Such an experience is quite lacking from a mobile device standpoint (see my post on The Myth of WORA).
EDIT January 30, 2012: It’s been nearly a year since I first posted this list, so much has changed since then. Rather than try to maintain this single post, I’ve created a github repository. Go there for the latest and greatest list. I encourage others to add their favorite links as well. I will keep this post active for posterity as well.
FYI, a year ago it was announced that henceforth, HTML5 would simply be known as HTML. Well, fast forward a year, and like it or not, it certainly appears that that the term HTML5 is alive and well. In fact, the HTML5 logo is littered throughout the web in support of this term. So much for Ian Hickson’s decree.
For years, businesses have searched for the holy grail of the development world – the notion of being able to write a program, application, app, or whatever they’re now calling it, just once, while being able to deploy it on any number of systems. Hence the term “Write Once Run Anywhere”, a.k.a. WORA.
Ok, so it’s been several months since my first installment of this blog post. I guess I was hoping that if I waited long enough that the next five most compelling technologies would reveal themselves. No such luck. I was left to my own devices to sniff them out. So, without further ado, here are the other five technologies to keep an eye on:
This is part two of a two-part post.
Unless you’ve been living under a rock for the past 6 weeks, I’m sure by now you are aware of Apple’s decision to change the function of that little switch located on the upper right hand side of the iPad, just above the volume switches. It was doing fine and dandy as the tablet’s orientation switch, allowing you to lock the orientation of the iPad regardless of how the device is being held or propped up.
Well, with the release of iOS 4.2 to the iPad, comes a change that frankly doesn’t make a whole lot of sense to me. That switch now becomes a mute switch! Hunh? It’s not like we didn’t have that capability already – just hold down the ‘Volume Down’ button to achieve the same result.
Don’t get me wrong, this is not an earth shattering decision, but frankly, it is quite surprising coming from a company that prides itself in providing world class user experience. They could have at least provided the user with an option to use the switch as they wish.
So I just don’t get it. Maybe someone can explain Apple’s rationale to me in the comments section. I haven’t seen or heard one person blog, tweet, or speak of their happiness with Apple’s decision. If you do, please enlighten me as to why.