- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Sat, 17 Jan 2015 06:42:36 +0100
- To: Web Payments CG <public-webpayments@w3.org>
Hi Guys, In theory a browser-based Web-app could do the same things as native applications, right? The fact is that it does not and that the gap isn't diminishing. If we take my favorite topic ("Secure AND Convenient Payments on the Web"), Apple Pay and similar show that local wallets reign. Trying to put wallets in the browser is a technical (but to date unverified) possibility but the more I look into this the less attractive it appears to be. Why would users and vendors be interested in maintaining *two* different wallet environments? Wouldn't it be easier (well, "easy" isn't the right word here...) to rather "call" the local (native) wallet from the browser to maintain a *unified* Look-and-feel/Security/API/Etc/Etc? I don't see this as a failure but as a *pragmatic* and *market-oriented* way forward. FWIW, this is at least what I will waste my limited cycles on this year. I wouldn't be surprised if Apple already has this going but if you bet on full distribution (=not relying on a central "SuperProvider") there's still a slim chance making a change. What about server-wallets? Well, that's already done, it is called PayPal. Best Anders
Received on Saturday, 17 January 2015 05:43:13 UTC