Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)

There was a previous idea that in the absence of an `id` then this will take the shape of the default fallback `manifest id`, which is the start_url and if there isn't a manifest file or start_url this falls back to the document url. But this doesn't meant that there is no id. it'll just be a computed automatic one that wouldn't allow the option to group several pages of a website as the same content/app. 

The upside is that the developer gets to call `navigator.install()` instead of `navigator.install('shoeapp')`, but then the downside is if `shoeapp.com` has an install button on its header it can quickly allow for multiple installations of the same app and the platform would treat them as different ones, and that would be messy for end users.

considering how much web dev gets done by copy and pasting code samples from stackoverflow or MDN web docs I think the developer simplicity of not requiring an arbitrary id will come and bite back in the future when users have N of the same apps installed because they were installed from different pages, even though they are related/the same app. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/888#issuecomment-2285897018
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/888/2285897018@github.com>