An interesting consideration here is when, if ever, we pass these data requests on to a third-party app like the payment app. In some cases this complicates things because the data is used to calculate the price but I'd expect data like email to be something a user's payment app would be readily able to provide. I can understand @adrianba 's logic about keeping simple and iterating but I am concerned that our ability to change the shape of the API in the future is limited and where we set the bar in terms of number of data points before we change _how_ this is done. At what point do we say we need to change? Is it when there are 5 different data points to request or 10 or never? When do we decide that this is working or not and how do we decide that? Who will have the data to back up an assertion either way. Finally, I'd be very interested to hear if there is a way we could A/B test this --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/pull/65#issuecomment-215654680
Received on Friday, 29 April 2016 08:11:00 UTC