Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)

> @adrianhopebailie You should only think of native messaging as a more powerful version of Android Intents because that's all it is claimed to be.

Then what does it have to do with the payment API? If native messaging was standardised within W3C then I'd consider messaging between the payee website and a native app in scope for us to standardize. Since it's not, I don't.

If we continue on the track we are on nothing will change in future if native messaging becomes a standard. Payment Apps (deployed as javascript running in the browser within a context bound to the origin of the publisher) will just have an additional standardized way to communicate with a native app. It will simply add more options, I'm not convinced it will enable anything new.

Note that the payment app javascript may run in a non-visual context so as far as the end-user is concerned the website is invoking a native app when the payment app javascript invokes the native payment app.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/156#issuecomment-232367591