- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Fri, 24 Apr 2015 10:48:40 -0400
- To: public-webpayments@w3.org
On 04/24/2015 10:12 AM, Anders Rundgren wrote: > On 2015-04-24 15:47, Tony Camero wrote: >> 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. > > It is the opposite that doesn't work smoothly, making > Web(browser)-payments a difficult target for innovation. I think, at least to start, the browser would function primarily as a decision assistant and a conduit for ferrying messages between the various participants in the payment process. That should, in no way, get in the way of innovation by payment applications, providers, etc. Rather, it will assist them by letting them function with a standardized set of expectations. Also, note that a "user agent" or "payment agent" isn't limited to a "browser", rather a browser is one example of a piece of software that implements (or would implement) it. > > Anders > >> >> On Fri, Apr 24, 2015 at 6:25 AM, Anders Rundgren >> <anders.rundgren.net@gmail.com >> <mailto: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 >> >> > > -- Dave Longley CTO Digital Bazaar, Inc. http://digitalbazaar.com
Received on Friday, 24 April 2015 14:49:03 UTC