Re: [browser-payment-api] [architecture] Use "user agent", not "browser" (#59)

I agree that this document is specifically about the payment api as it is reflected in browser-like environments.  I just want to believe that it is possible to support the architecture in other sorts of user agents (e.g., a mobile application with in-application payments should be able to access this interface / environment.)  After all, any UX related to this API is at the "chrome" level of the environment.  That should be accessible from user-space application that is acting as the agent between a user and whatever they are doing.  A good example would be the shopping app from newegg.  When I am in there and press buy, I want to use my chosen "wallet" to select payment instruments, provide shipping address, whatever.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/59#issuecomment-196380140