Re: [w3c/webpayments-payment-apps-api] Suggested apps (#74)

@rsolomakhin,

This sounds like the same intent of the "Recommended payment apps" described in the spec. Thank you for digging down into the next level of detail. Can we agree to call them "recommended payment apps" instead of "suggested payment apps" simply because the former term has been used for a longer period of time?

Some notes:

* Yes, we need payment app identifiers. Those identifiers will allow the browser, for example, to determine whether a recommended payment app has already been installed and is ready to make payments, in which case, the browser can enable  user configuration (for example) to "show recommended payment apps that are enabled" at the top of the list. (That's just an example.)
* We have talked in the past about recommended payment apps being "ready to use without requiring registration". Registration should not be required to use the app for the current transaction, but is important for persistent use. Therefore, I agree with "SHOULD " have a payment app manifest. And also the user agent MAY offer the user the opportunity to register the payment app. (or that may happen automatically on configuration, as in "Whenever I choose to pay with a recommended payment app, automatically register it for me for future use."
* You wrote "Once the payment app is installed." I am using terms this way: registration means "provide metadata to the browser" and installation means "install a piece of software in the operating system." So, for native payment apps, installation may be necessary. (And installation may lead to registration, if the operating system determines that software installation is one way to register a payment app so that the browser learns about it through some OS mechanism.) But for Web-based payment apps, no registration (of the payment app with the browser) should be necessary for the current transaction.
(Please note here that I am NOT talking about whether the user must create an account with a payment app; that's a different kind of enrollment.)

Let me start there and see if those points resonate with. I'll put this on Wednesday's agenda.

Ian



-- 
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-payment-apps-api/issues/74#issuecomment-266517629