W3C home > Mailing lists > Public > public-webpayments@w3.org > April 2015

Re: [payment agent] Payment architecture feature priorities

From: Tony Camero <tonycamerobiz@gmail.com>
Date: Fri, 24 Apr 2015 08:47:42 -0500
Message-ID: <CAJqDFU+A_qEsk_oeJPLedgrxRXhBLHeT6q3drDwKWOmK4xMi7g@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: Web Payments CG <public-webpayments@w3.org>, "public-webpayments-comments@w3.org" <public-webpayments-comments@w3.org>, Dave Raggett <dsr@w3.org>
Why would the the building blocks/protocols for web payments not directly
migrate into native apps?  Any native app could certainly meet the
requirements set for a web payments. It seems inclusive to me.

On Fri, Apr 24, 2015 at 6:25 AM, Anders Rundgren <
anders.rundgren.net@gmail.com> wrote:

>
> https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0145.html
>
> "One suggestion is not to rule out local apps for the initial charter.
> W3C is seeking to close the gap with native, but this is a long term goal,
> and in the short term we should acknowledge that developers are likely to
> be attracted to native apps due to the richer capabilities available to
> native apps compared with web apps"
>
> Finally a description that matches the reality!
>
> Browsers are static bloated "monoliths" that doesn't enable third-party
> innovation.
>
> Anders
>
>
Received on Friday, 24 April 2015 13:48:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:39 UTC