[w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34)

Hi All,

Thank you for drafting up the [spec](https://w3c.github.io/webpayments-payment-apps-api/). Here are my initial thoughts from the standpoint of a browser implementer. Let's discuss this in further detail.

### Registration

I am of the opinion that installing a payment app is sufficient to register it. On the web, this can be accomplished via registering a [Service Worker](https://github.com/w3c/webpayments-payment-apps-api/issues/33#issuecomment-242895193) and there's no need for additional `navigator.payments.register(info)` API. Operating systems have their own concepts of installing native apps, but the spec should not concern itself with native app much, if at all.

### Payment options

The spec allows payment apps to take up several lines on user screen via a concept of "payment options." (For example, if BobPay is a credit card wallet, then it can show `BobPay Visa*1111` and `BobPay MasterCard*5454` as payment option.) I have heard feedback that this may not be desirable for the first iteration of the payment app spec, because it's one more layer of abstraction with marginal benefit. Let's stick with one-to-one mapping here for now. So BobPay should be able to display only one item on browser UI: "BobPay".

### Network considerations

The spec talks about network failures. I think Service Workers are the answer here. They provide offline capability and caching, if necessary.



-- 
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/34