Skip to main content

Going native

This afternoon I was pleasantly surprised to see the announcement that Facebook for iOS has gone fully native. Previous to today, the Facebook app has been a viewer to HTML5 based content that was mostly functional, but slow. The old app was adequate, but not stellar. When I fired up the new app I was greeted with a much nicer user experience in regards to smoother scrolling, and cleaner animations. Overall, it was a positive change, although it still does nothing to combat the incredibly content heavy feed that Facebook shoves at your phone. At least I get smoother scrolling while I'm waiting for all my content to take forever to load.

But this all got me thinking about the how far we've come in regards to write-once-run-anywhere promises of the web of the early 2000's. For a big part of my IT career everything seemed to be focused on a movement to make HTML everywhere, a ubiquitous language that could present it's content to all corners of the ever-more-connected globe. But HTML had some serious flaws. First, it's not really an interactive programming language with all the rich features of control structures and variables, so along comes JavaScript to save the day. In fact JavaScript was a huge boon to static web based content, and quickly became the defacto dynamic page language. Perhaps these two together could conquer the world and make it possible to create a single app for every circumstance?

The dream was almost realized fully with Palm's WebOS. Here you had a fully featured smartphone operating system that had as it's core, HTML and JavaScript. For the most part it was a great idea, but it got destroyed by poor hardware, that couldn't keep up with the demands of a fully interpreted system language. Eventually Palm released a native SDK so that developers could go back to writing low level, compiled applications that took full advantage of every possible memory bit and CPU cycle. Native had once again won the day.

Although specialized toolkits such as PhoneGap try to continue to bridge the gap and allow the vision of write-once to continue, even most developers understand that abstraction toolkits end up costing in the end. Especially as an application continues to grow, it usually becomes apparent that, despite their usefulness, toolkits often can't keep up at the same pace as an investment in a native application.

So today once again, native has become the choice for what is probably the most installed app on the planet. The dream of being able to utilize the universality of HTML5 came to a halt, as users breathed a collective sigh of relief, and waiting for Facebook's servers to respond to another smoothly scrolled pull down reload request...

Comments

Popular posts from this blog

I love typing on my iPad

Ok, before you think I've gone crazy and suddenly believe I like smacking away at a non-responsive touch-screen, let me clarify that title... "I love typing on my bluetooth keyboard on my iPad." Like many people, I took the plunge and got a wireless keyboard for my iPad, because for any serious typing work, you really can't beat the smooth responsiveness of the Apple Wireless keyboard. But, just to clarify things further, it's not the bluetooth keyboard that is the reason I love typing on my iPad. Let's correct that title one more time... "I love writing on my bluetooth keyboard on my iPad." There we go, that's better, and it gets to the heart of what I wanted to share in this post. I'm going to make a bold statement, which I'm sure tons of people will find issue with, but here is it. The iPad is a perfect writing tool. Ya, that's right. I just said that a small 10 inch device that you need to purchase an additional keyboard for

I don't have a wood shop...

It's been a few weeks since my last entry on this site, and there's been a good reason. No, it's not because there hasn't been anything interesting to write about, I certainly didn't take advantage of many good opportunities to write about tech news. It has been for a simple, somewhat silly reason. The new Warcraft expansion launched. I hear the groans now, all the way through the ether. People screaming "Oh no... he's one of THEM!" Well, sorry to disappoint, but yes, I am "one of them". But, some clarification is in order. I don't abandon my family to play WoW, I get my work done, I don't call in sick, etc., etc.,. However, it does bring up an interesting new phenomenon in our modern society. Gaming as a hobby. It's long been a staple of adult life to fill our time with hobbies and pastimes that give us something to do beyond work, but yet challenge us a bit mentally or physically. Video gaming has been around only a few deca

Where in the world am I?

This week saw the launch of iOS6, the latest in Apple's mobile operating system iterations. For the most part, it's been a decent incremental upgrade, with lots of new little tweaks, such as Facebook integration, and the ability to update applications without inputing a password. However, the big feature that's been getting all the press is the new mapping app. In Apple's bid to rid themselves of Google "taint", they decided to make their own mapping service, but I think it's become very apparent, that it's not as easy as it looks. Many places are mis-located, or labels are wrong (especially internationally), causing no end to the hilarity of people posting screenshots of mistakes. There's a reason why Google Maps is king, and it's based on why my friend Wes so aptly put forth, that Google is a data company, and Apple is not (yet). Providing good mapping data requires good... well... data. Google has it. Apple, and other competitors don't