Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33)

@rsolomakhin I agree that manifests are very useful but I think you are conflating payment app manifests and payment method manifests.

A payment method manifest (like `https://bobpay.xyz/payment-manifest.json`) describes the payment method, including the id's of apps that are allowed to handle payment requests for that method. This is a new concept and we need to design these but I don't think they should contain anything about payment apps other than the id's of those that support the payment method (a foreign key relationship).

I think we'd also get some value out of using payment app manifests too and should be leveraging the existing work done on [appmanifest](https://www.w3.org/TR/appmanifest/). This is where we'd define things like the app icons, label and alternative versions in app stores etc. (This is all already defined for app manifest).

App manifest also has extension points which we can use to define payment app meta data like supported payment methods: https://www.w3.org/TR/appmanifest/#extensibility

-- 
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/33#issuecomment-245402005