Re: [w3c/payment-handler] Add userHint to PaymentManager (#206)

@dlongley asked:

"Can you provide some of the rationale for not displaying individual payment instruments?"

You might mean different things in that question:

a) Why wouldn't a browser display all the payment instruments managed by a payment handler? Google colleagues have said they do not plan do to that, and the reasons include (on mobile) screen real estate. Other browser might display all instruments, or might do so on desktop by not mobile.

b) Why not modify the "name" of one of the payment instruments as a user hint? That could work, but the question is "which one would be the best?" and this proposal suggests that the payment app may have information on what would be useful.

Having recently spoken with Mozilla and Google, here are the user experiences I expect when I click on a payment handler, either:

1) Launch the payment handler and let the user choose 1 payment instrument from among multiple ones. The payment handler itself might support rapid selection of certain payment instruments.

2) Show all the payment instruments and let the user select each one directly.

Both of those behaviors (and possibly others) are supported by the current specification. 
The "userHint" proposal does not alter those possibilities. @rsolomakhin mentioned some
user experience with shipping addresses that suggested that a user hint could help
people select payment apps.

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/payment-handler/pull/206#issuecomment-325001485