Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) from Marcos Cáceres on 2017-02-08 (public-webpayments-specs@w3.org from February 2017)

From: Marcos Cáceres <notifications@github.com>
Date: Wed, 08 Feb 2017 03:36:33 -0800
To: w3c/webpayments-payment-apps-api <webpayments-payment-apps-api@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments-payment-apps-api/issues/98/278304294@github.com>

I honestly don't think we need this. Look at how elegantly you can already do profiles in Uber, for instance: 

![screenshot 2017-02-08 22 33 59](https://cloud.githubusercontent.com/assets/870154/22735636/b289693a-ee4e-11e6-8d5e-98f197ce7ee5.png)

You can just do it in the same app, and the app remembers... that's the whole point of having these be PWAs. Exposing multiple app and profiles doesn't make sense (to me)... it probably doesn't even make much sense to show the payment methods: only the icon for the PWA that handles the payment (again, see above... just pretend Uber is a PWA).  


-- 
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/98#issuecomment-278304294

Received on Wednesday, 8 February 2017 11:37:10 UTC