On 24 April 2015 at 16:12, Anders Rundgren <anders.rundgren.net@gmail.com> 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 agree the browser is a difficult platform for payments innovation. But I dont think it's impossible. My testing so far has been mainly in the browser. I agree it's very difficult, but I dont think it's impossible. I am finding decentralized payments so far to be incredibly powerful, but I dont think they are for everyone. So maybe the barriers are not the world thing. > > 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 >> >> >> > >
Received on Friday, 24 April 2015 15:35:42 UTC