Google I/O 2013

With Google I/O approaching it is time to start speculating...

Last year the keynotes at Google I/O were very different in tone; the one for Android and the one for Chrome OS. It will be interesting to see if there is any big change this year, now that Sundar Pichai will - indirectly - have a role in both.

Google's commitment to the web and the evolution of Chrome has taken them to an extraordinary place.  Soon it will be possible to develop apps using standard web technologies and deploy them to a wide range of environments; desktops running OS X, Linus or Windows as well as Chrome OS.

There seems to be a genuine desire to get Chrome apps to play nice in their host environments, not just within the browser. For example the launcher that was part of Chrome OS now has a variant in some desktop environments.

The Chromebook Pixel has a touch screen, so developing Chrome apps for a touch interface is clearly on the agenda.

So isn't it about time for Chrome apps on Android?*

Of course that question betrays my own prejudices. It may be completely at odds with reality - others have suggested that we may see Android apps on Chrome OS. But to my mind Chrome apps on Android would take you perilously close to what is now the almost forgotten dream of "write once, run anywhere".

Chrome apps launched from bookmarks with full-sized icons, running full-screen and appearing in the recently used applications screen would play nice with true Android apps.

 So maybe not so much speculation as wishful thinking...

 *"Chrome apps and extensions are currently not supported on Chrome for Android. We have no plans to announce at this time."


Comments

Post a Comment

Popular posts from this blog

SmartLink

Image
In a previous post I tried to describe how I thought technologies like SmartTags and AutoLink ought to behave. With greasemonkey in Firefox I've been able to build a proof-of-concept demonstrator. For the moment I'm calling it Smart Tag/Auto Link. SmartLink is based upon the idea that content authors should mark-up content that can be 'smart-linked', using standard XHTML constructs. This has two advantages: it effectively provides an 'opt-in' mechanism for content providers it doesn't require 'magic' to identify what can be smart-linked and thus provides a much more extensible approach. of course there is one fairly major disadvantage: there isn't any suitably marked-up content out there, with the exception of some test posts I've put together for the purpose. Getting Started If you want to know a bit more about SmartLink then click here . Alternatively if you want to see how SmartLink behaves and you're using Firefox t
Read more

A Review of hReview

microformats may well represent a path from where we are today to the [lowercase] semantic web. If so, one of the first waypoints along such a path could be the emergence of aggregators capable of taking advantage of suitably marked-up content. Applying a 'microformat' approach to tagging, Technorati introduced the rel="tag" approach to marking-up tags. Technorati also supply the corresponding aggregation service, e.g. see posts tagged with microformat . Given this minimalist approach to tagging, the hReview specification comes as something of a surprise. It seems to represent a format developed independently of the environment in which it is most likely to be used. The rel="tag" approach makes a major, simplifying assumption. This is that the tag refers 'to a major portion of the current page (i.e. a blog post)' . I am assuming that it could apply equally to a blog entry in an RSS/Atom feed. Thus an aggregator can associate a tag with two p
Read more

Speculations about developing with iCloud

It's been three months since Apple revealed it's vision of the cloud to the world. After its introduction, much was written (e.g. It Just Works ) about how iCloud compares 'philosophically' with others, most obviously Google. Now, supposedly close to launch and with iCloud in the hands of developers, there seems to be surprisingly little written about how that philosophy translates into developing a modern iOS app. Apple promises consumers that things 'will just work'. Just keep using apps in the same way and they will magically remain up-to-date across all your devices - in truth I'm not sure more magic was promised. Apple might be making a similar offer to developers. In principle iCloud means that an ObjectiveC developer with XCode can create and distribute apps containing this magical ingredient without having to learn any new skills, without having to develop any cloud-based components at all. What's more, with relatively little extra work, they c
Read more