Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)

I think all of @jnormore’s comments in this thread are worth paying very careful attention to; e.g.:
> From a merchant perspective, I would want to provide the customer with the most streamlined checkout possible, which IMO would mean that if they don't have a payment type enabled I could make it easy to enable that in the checkout flow itself
> ...
> You cited Apple Pay as an example, I wouldn't use this as a good example of an ideal case from a merchant or customer perspective, requiring the customer to jump out to a separate application (or multiple) to enable it is really bad for checkout conversion
> ...
> The merchant wants the customer to have the ability to check out as easily as possible, to sell their products, so it's their job to give them the most seamless way to onboard to those payment methods as possible while not distracting from the original intent to purchase

I do not think the importance of the overall point that @jnormore is making here can be overstated.

We all are here to solve problems for end users ultimately, and IMHO we should always be careful in everything we do to preserve the primacy of user experience over other concerns. 

Solutions that help to address problems for other non-user constituencies involved are net bad on balance if the cost of them is that they degrade the user experience or disrupt or intrude into the normal user interaction/expectations for sites/services they want to get something done with.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:

Received on Friday, 29 July 2016 04:46:46 UTC