Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494)

@adrianhopebailie @marcoscaceres Being forced using "workarounds" limits the value of an API.  The need/utility for this kind of communication were not envisioned. 

I'm indeed using exactly the scheme you mention in the Android version of my PoC. Compared to the PC version which is only using the "chatty" interface (through _Native Messaging_), the Android application is _way more complex_ and the same goes for the Android-specific merchant integration part.

It is also worth mentioning that in the PC implementation (using the "chatty" interface), all external communication is performed through the browser (using <code>fetch()</code>)and thus _adhering to browser rules_.

Finally, the most important reason for this arrangement is that it enables the payment application to be used in other scenarios with very moderate changes.

In effect you leave me no choice but continue on this path:
https://lists.w3.org/Archives/Public/public-webpayments-ig/2016Dec/0026.html

-- 
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/browser-payment-api/issues/494#issuecomment-291054328