W3C home > Mailing lists > Public > www-tag@w3.org > September 2015

Re: Foreign-fecth: Was: Proposal: Uniting the Web and "App" worlds

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Thu, 17 Sep 2015 06:16:26 +0200
To: Marijn Kruisselbrink <mek@chromium.org>
Cc: Alex Russell <slightlyoff@google.com>, "www-tag@w3.org List" <www-tag@w3.org>, Jungkee Song <jungkee.song@samsung.com>
Message-ID: <55FA3E9A.9030300@gmail.com>
On 2015-09-16 20:55, Marijn Kruisselbrink wrote:

 > what you're asking for is not really the client side API for this,
 > but some standardized (hopefully cross browser) way to implement
 > the native side of this. Maybe some standardized way a native application
 > could register itself with a webbrowser to handle certain actions from websites?
 > I know various people have been thinking about this problem space, although I'm
 > not quite sure what the current status of that is. And there have of course been
 > various attempts in the past. Actually standardizing something of how a browser
 > interacts with the native operating system is of course complicated.

 > I'm not quite convinced yet that it is something that makes sense to do,
 > although it certainly seems like an area worth exploring.

You don't have to go particularly far to find a "customer" :-)

A Wallet that doesn't work on the Web is simply put "lame", isn't it?

AFAIK our friends in Cupertino have a similar problem...

When it comes to technical solutions I would be a bit cautious about overloading
APIs like foreign-fetch because the requirements seem pretty different for invoking
and communicating with local applications, and for accessing remote Web resources.

The idea is not creating a "workaround" like Chrome's Native Messaging, but making
[specially crafted] native "Apps" first class citizens on the Web.

Anders R
Received on Thursday, 17 September 2015 04:17:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:12 UTC