« | Blog Home | »

Platform Agnostic and Current Friendly

One of the great promises of HTML5 with CSS3 and Javascript is that eventually, after much wrangling & negotiation, one will be able to write apps that can work across many devices regardless of platform and ecosystem. In the meantime, while we are waiting for HTML5 to have access to the contacts or camera on the mobile you could be possibly carrying, we can use future friendly practices to develop and design flexible web sites and apps.
Until the future web accessible world arrives, from a pragmatic standpoint, many of us if we want to access contacts, or the camera, or a variety of other APIs and features on our mobile devices, we find ourselves delving into hybrid native-web mobile worlds or diving into native mobile apps be it through a SDK or PhoneGap or the like.
Thomas Perl in a post-Nokia World 2011 blog post, Comparing Mobile OS SDK availability by platform, builds an argument for a very salient point for folks who are currently developing for native mobile apps:

“Now, people can argue that one can set up dual-boot or virtual machines to support all OSes, but that’s not the point. The point is that if the SDK is available on all Desktop platforms (note that this is not the same as SDK targetting all mobile platforms), developers can retain their choice of Desktop OS on which they develop on, and are not forced to use OS X or Windows for development of apps for the corresponding mobile platform (I also understand the reason why these companies only provide the SDK for their own Desktop platform, but that is not a good reason from a developer’s point of view).”

I agree with Mr. Perl. I don’t want to be told which desktop platform I must use so that I can develop for a certain mobile. I find working in virtual box to be tedious after a short span of time. I would like the system I develop for to respect me enough to let me to make the choice about what desktop/laptop OS I prefer to use.
Bravo to Android, Qt, and PhoneGap.