Blog Post

Chrome Apps 101: Video shows Google’s vision of future web apps on mobile and desktop

The future of Chrome as a strategic platform was on center-stage last month. At its Chrome Developer Summit, Google(s goog) shared a number of presentations, but one in particular stands out in light of two recent events: Microsoft’s Scroogled ads and recent news that Chrome apps would be coming to mobile devices; this was actually already demonstrated back in May at Google I/O.

This recent 30 minute presentation from Google Chrome Developer Advocate, Joe Marini, is worth the watch to see where Google is headed when it comes to web and native apps on the desktop and mobiles.

Marini highlights five key functions that Chrome Apps offer developers, namely:

  1. The apps run offline by default.
  2. They run on multiple platforms: Windows(s msft), Mac(s aapl), Linux, iOS and Android.
  3. Deep access to platform functions and hardware.
  4. A rich, engaging user experience is possible.
  5. All distribution and updates are centrally handled by the Chrome App Store.

For those who haven’t been following Chrome of late, these apps are a key element in Google’s Chrome strategy to boost engagement with Google services on desktops, laptops, smartphones and tablets. As long as a device is running the Chrome framework, it can use these Chrome Apps which can run outside of the browser.

About three minutes in, Marini shows a web app to control the colors of a connected Hue light bulb, for example. And there’s even a central notification service supported by Chrome that Marini notes can “wake up” the browser when it isn’t running so that it can notify users of new information.

This photo is a good example of item no. 3: Chrome apps having hardware access on different platforms. Here I’m running the Chrome Camera app on a Microsoft Surface device and yes, my mind is blown by how this app accesses the camera no differently than a native app; there’s no plug-in involved and no hoops to jump through.

surface camera app

While Google is providing the tools and framework for this new breed of apps, there’s no guarantee of success. Even as a Chromebook Pixel owner, I know that.

The company has to convince developers that building Chrome Apps is to their advantage. That may be a tough sell when native apps are the current standard. The fact that iOS developers are collectively making billions of dollars for their mobile apps is another obstacle; how can Google convince these programmers to build for Chrome?

It’s going to take a while, if it happens at all, for a number of reasons. Chrome App capabilities are still maturing, for one. Until a developer can create exactly the app they — or rather, their users — want with HTML, CSS and JavaScript, native programming techniques and languages will still rule the roost. There is the alternative of Google’s Native Client technology, which takes a C or C++ app and wraps it up for use on a device with Chrome, but even that won’t appeal to many devs at first.

google keep

Still, the tools that Google is offering provides a chance for change. After watching the full video — and seeing another demonstration of a Chrome App running both on a desktop and a smartphone — I think the company is on to a potential paradigm shift. It doesn’t matter what I think though: It’s all up to developers at this point and I’m certain Google will be doing everything it can to continue wooing them because of what’s at stake: The attention of billions of app users around the globe.

4 Responses to “Chrome Apps 101: Video shows Google’s vision of future web apps on mobile and desktop”

  1. Everypost

    Great post and very informative. To me, now that we know what Google is seeking to accomplish the next question needs to be whether developers will go for it? Will native apps still rule the world and if so, why? What shift are we going to see in the coming year in response to the offering Chrome Apps has for developers?

  2. Suparna Rao

    Kevin, predictions about the demise of native apps are rising. They may not be needed everywhere, they may over-qualify for some requirements, but where they fit, they’re irreplaceable. And that is just one of the reasons why native apps won’t die..ever. For more..

  3. Kevin, why don’t you also mention 1 very important reason (hidden behind all obvious ones) that our beloved Chrome has a tough road ahead with respect to getting developers trust –
    TOTAL NEGLECT of developers!

    With all due respect to Joe Marini (who seems to be the only one who cares about devs) go ahead & take a look at the forum to get a sense of google (UN)Support:!forum/chromium-apps

    Even FB at least warns devs ahead of time prior to their endless changes – Google castrates its APIs on a whim as they did last November with just a sudden blog post & no prior roadmap warnings wharsover

    There’s definitely someone up there along the management chain who has to change his or her attitude towards devs or let others do a better job…