W3C home > Mailing lists > Public > public-browserext@w3.org > May 2016

More details on the Google native messaging variant

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Mon, 23 May 2016 19:32:37 +0200
To: "public-browserext@w3.org" <public-browserext@w3.org>
Message-ID: <7c4a8b8a-5dc8-0c83-e7dd-096163bdc67e@gmail.com>
This seems to be closer to what I'm advocating.


-------- Forwarded Message --------
Subject: 	Re: Google I/O talk about PaymentRequest
Date: 	Mon, 23 May 2016 16:30:33 +0000
From: 	Rouslan Solomakhin <rouslan@google.com>
To: 	Anders Rundgren <anders.rundgren.net@gmail.com>
CC: 	Adrian Hope-Bailie <adrian@hopebailie.com>, Ian Jacobs <ij@w3.org>, Payments WG <public-payments-wg@w3.org>



We are prototyping now, but the web developers cannot access our prototypes yet. Third-party integration means two things:

1) Chrome provides a way for any app to say "I am a payment app". This includes both native apps and websites.
2) A developer of a payment app modifies their App to hook into Chrome.

Website-based payment apps are being discussed in this WG now. I'd like to define Android native payment app API as well. I expect it to be intent-based. That way an browser on Android can talk to any Android native payment app via the package manager. Stay tuned for updates.

The reason for the stretched out time-line is mostly due to engineering and planning. Testing, integration, productionizing, UI polish---all of that takes time.

On Mon, May 23, 2016 at 1:39 AM Anders Rundgren <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote:

    On 2016-05-22 20:46, Rouslan Solomakhin wrote:
     > Thank you! Let's build something great together :-D

    In the video at 26:20 there is a slide saying that third-party application
    integration is slated for "Early 2017".  Does this mean that you cannot even
    prototype now, although there's a beta browser supporting the current
    Web Payment API?  I don't really understand what you mean with third-party
    integration either, what exactly is required from Google's side?

    Anders


     >
     > On Fri, May 20, 2016 at 11:03 PM Adrian Hope-Bailie <adrian@hopebailie.com <mailto:adrian@hopebailie.com> <mailto:adrian@hopebailie.com <mailto:adrian@hopebailie.com>>> wrote:
     >
     >     Great work Rouslan!
     >
     >     Looking forward to getting a lot more developer eyes on the work now.
     >
     >     On Saturday, May 21, 2016, Ian Jacobs <ij@w3.org <mailto:ij@w3.org> <mailto:ij@w3.org <mailto:ij@w3.org>>> wrote:
     >
     >         Hi all,
     >
     >         Today at Google I/O, Rouslan and Alex Sieke presented PaymentRequest in:
     >
     >           Bringing seamless checkouts to the mobile web
     > https://youtu.be/yelPlCVZLEE
     >
     >         Congrats to both of them and many thanks for inviting developers and
     >         merchants to help improve the API by commenting on the spec.
     >
     >         I was glad to see these goals for the API emphasized:
     >
     >          * Cross-browser
     >          * Cross-device
     >          * Open ecosystem (which touched on both “any payment method” and “third party apps”).
     >
     >         Have a good weekend,
     >
     >         Ian
     >
     >         --
     >         Ian Jacobs <ij@w3.org <mailto:ij@w3.org>> http://www.w3.org/People/Jacobs
     >         Tel:                       +1 718 260 9447
     >
     >
     >
     >
     >
     >     --
     >     Sent from a mobile device, please excuse any typos
     >
Received on Monday, 23 May 2016 17:33:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:10:00 UTC