> I would still like to be able to use PaymentInstrument store to create parts of the UI in the web application. Conveniently, it's what I wanted to show here ("wallet.com" graphic): #98 (comment)
I had not considered that requirement.
@annevk don't get me wrong, I think we need to consider these things but should avoid putting UX mandates in the spec.
i.e. Does the developer have a good interface to manage instruments that works for all use cases (now also considering this one from @marcoscaceres )? If yes, then let's leave UX around persistence of the data to implementors.
Specifying the lifecycle of this data is not an interoperability concern, unless there is some desire to share that data across implementations, which I have heard strong aversion to.
--
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/issues/236#issuecomment-349908961
Received on Thursday, 7 December 2017 09:18:46 UTC