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

Thanks for this summary @tommythorsen, this is very helpful.

I am not an expert on how browsers operate internally but the architect in me says option 2 is the best way forward at list until we decide we have to go to option 3.

I see an advantage in option 1 in that it's simple and means re-using existing primitives which is good. Perhaps we could still follow option 1 but instead of having a payment request event just listen for messages and look at the message to see if it's a payment request?

I'd like us to consider carefully the possibility of re-looking at using manifests for payment apps where perhaps the app has no `start_url` but rather just a service worker (See https://github.com/w3c/manifest/issues/161 for discussion of this lately, I think we have a compelling use case).

Browsers that see the manifest `rel` link will fetch the manifest, see it is for a payment app and prompt the user to register it. If the user accepts then they will register the payment app (service worker). 

Worth getting feedback here from @marcoscaceres and @jakearchibald, I suggest we try to meet at TPAC as they will need a lot of context.

-- 
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-242732079