3 ms·
> How does this make developers' lives easier than existing solutions? I'm kinda thinking it doesn't. One way it makes developers' lives easier is by providing
by objclxt 9y ago
> How does this make developers' lives easier than existing solutions? I'm kinda thinking it doesn't.
One way it makes developers' lives easier is by providing a single API through which you can offer multiple payment services (Apple Pay, Android Pay, PayPal, etc), rather than requiring separate integrations and code for each service.
However, the main attraction is it gets rid of auto-fill - which is frequently clunky - and replaces it with a unified check-out process. The benefit there is for the user, not the developer.
> Odd that none of the editors are, you know, actually from companies that do meaningful e-commerce.
Being an editor of a spec doesn't really mean much in terms of defining it. It just means you're the point person for a ton of administrative work.
The group has very active participation from a number of eCommerce players, including all the major card networks, AirBnB, Shopify, Stripe, Tencent, Worldpay, and Yandex. There's a lot of eCommerce interest: https://www.w3.org/2004/01/pp-impl/83744/status https://www.w3.org/2004/01/pp-impl/83744/status
- pcl 9y ago> the main attraction is it gets rid of auto-fill - which is frequently clunky Not only is auto-fill clunky, it's also tricky to implement securely. Moving these semantics into a dedicated API should help get the browsers out of these sorts of cat-and-mouse games. See previous discussion: https://news.ycombinator.com/item?id=13329525 https://news.ycombinator.com/item?id=13329525