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...

Popular posts from this blog

Push it... push it real good...

The other day I got a chance to play with the new Apple force touch trackpad. This is a new design that Apple has put on their laptops for non-mechanized clicking on trackpad. When you press on the trackpad it senses the force that you're pressing with, and when you reach a certain level, you feel a 'click'. If you keep pressing, you feel a second 'click'. The unique thing is that these 'clicks' aren't physical in nature. The trackpad never moves at all, but the click that you feel is from haptic feedback. In essence, when you press with enough force, the trackpad clicks back at you. You feel the sensation of clicking, but it's simply the trackpad responding to your pressure.

I got to play with this for a while, since the Apple Store rep was talking with us about soccer, and after a short bit I was getting the hang of it. I feel that it would take quite a bit longer though to really feel comfortable with this new paradigm. I'm someone who has a …

Hack! Slash! Burn! Crush!!

The big tech news story of the weekend was the hacked account of Mat Honan. As documented in his posting on Wired.com, in the space of a few hours his digital life was in shambles. And as much as we always talk about strong passwords, etc., this was not a case of password failure. It was a case that shows just how our desire for on-demand, cloud based services that are convenient can come back to haunt us.

I highly suggest you go read all 4 pages of the article, but the quick summary is that a hacker wanted control of Mr. Honan's Twitter account. In order to get it, they started with basic social scouting, and proceeded to use all of the built-in tools of Google, Amazon and Apple to gain access to his accounts without ever needing to crack a single password. At Google they discovered what his Apple ID e-mail address was when they did a simple "Forgot my password" query. Then at Amazon, they called up customer service and game'd the system to get access to the last 4 …

The beat goes on

Yesterday Apple revealed their long awaited entry into the streaming music field. They were able to do this quickly because of the acquisition of Beats last year, and the systems and intellectual property that came with that purchase. Considering that the music reveal was pretty much the only big news out of a pretty benign developer keynote, I'll take a few moments to talk about what I think about it.

Apple was perhaps the defining company in the music revolution of the past 20 years. With the introduction of the iPod that revolutionized portable music, to the creation of the iTunes store and the eventual death of DRM, Apple has been at the forefront of digital music. This leadership comes with high expectations to continue to lead, and so many people have long questioned Apple not getting into the streaming music business quicker.

For the past few years new companies have come forth to lead the change in the streaming music evolution. From Pandora and its ability to create uniqu…