Ex-Apple Javascript Guru: HTML5 and Native Apps Can Live Together

8 thoughts on “Ex-Apple Javascript Guru: HTML5 and Native Apps Can Live Together”

  1. Ok, two things…

    1) Why ONLY HTML5?
    2) Why a whole new platform?

    This problem has already been solved. The solution uses all existing web standards, requires zero infrastructure changes, uses all existing programming techniques and works with HTML4 and HTML5. And it also works on all platforms.

    Seriously – you don’t need a new anything, you just need to make work what’s already in place. Why should I have learn another platform – there’s nothing wrong with what’s there.

    This is the best part of the article:

    “In the touch-based mobile device era, folks need to think of ways to have a single technology stack married to the ability to create unique experiences for different devices.”

    You’re so right. Let me know when you want to see a demo.

    Cheers,

    Peter
    5o9 Inc.

    1. Peter oh Peter, how thou art in such denial. Yes, its true, the human brain doesn’t like disruptive change. But Charles Jolley’s point of view makes sense (its “both” not “either or”). HTML5 is where its heading but not what the W3C would have predicted years ago with their committes cackling about the “semantic web”, etc. HTML5 is the puck and the intelligent Wayne Gretzky’s of the world know to skate to where the puck is going to end up. In the mean time there will a plethora of deniers and boo hiss hissers.

      1. Eddie,

        You misunderstood my post. The goal is simple, HTML4 and HTML5 (HTML5 is years a way from being a standard). Secondly make it work without having to learn a new platform. Thirdly figure out how to integrate with nothing more than a few lines of code.

        We were thinking beyond HTML5 years ago. For example – try this – using nothing more than HTML5 access the Unique Processor ID and the Storage device of a Blackberry device. Post the JavaScript that does that. Also do it in a way that allows me to reject the request and also if I do accept ensure that the meta data is encrypted back to the server.

        And for a bonus round – use the same code on Windows Mobile, iPhone, Android and Symbian.

        Not quite as easy to do as you think.

        Personally I don’t care who wins, HTML4, HTML5, HTML6, CSS2, CSS3 whatever. You’re solution should “seamlessly” support them all.

        Ours does.

        Cheers,

        Peter

  2. Fascinating. Fun.

    Cripes, Om. I spend a day or so without wandering through the many rooms of your cyber-bungalow and find too much to read through in one sitting.

    I’m going to have to catch up in the morning.

    1. @Eideard,

      This is an awesome report by the venerable Om Malik! The marriage of the clouds (think Structure 2010 conference) and the myriad of the ultra mobile connected devices (3 million iPads in 30 days, 10 million by end of Q4 2010 if Rupert Murdoch is right, and possibly another 20 million in 2011). Oh mama, Rupert Murdoch is going to be grinning ear to ear, as News Corp will be reinvented on the iPad. Think James Bond’s “Tomorrow Never Dies”. Its time to get super duper hyper way psyched! Where’s Curly from the 3 Stooges to deliver a few Nyuk Nyuk Nyuk’s to the financial news drones who can only focus their news coverage on recessions and job losses … Om Malik to the rescue and saves the world. Tomorrow Never Dies!

  3. So what do you promote to the user, an app to download or a url to bookmark? Crazy as it seems, although adding a url to your home screen is way simple, I’d bet most users who are trained to download apps would think, “huh, a webpage – that’s so 2006”. You and I know that’s silly – but I guarantee you users perceive apps as legit, quality, etc. So the part about using a native app as a wrapper intrigues me as the solution. But would that app make it safely through the Apple app police – because if it’s a wrapper can’t it just as easily serve porn as news? Or am I over-thinking it?

    Curious to hear how this would work and what others think about the perception issue.

    Chris

  4. Mr. Jolley isn’t the only Apple employee to go on to build his baby.

    Francisco Tolmasky who developed mobile safari and Maps for the iPhone, and Ross Boucher who worked on the recommendation engine for iTunes went on to startup a company called 280North focused on developing a true port of Cocoa to the browser called Cappuccino (http://cappuccino.org) the project as since exploded and today is a great solution for building cross browser desktop class applications in the browser.

This site uses Akismet to reduce spam. Learn how your comment data is processed.