Re: [w3c/manifest] New Boolean members to control interaction with related applications (#658)

> If they do have the native app installed, then subsequently installing the web app will create a terrible notifications experience, so this approach allows installation of the web app without creating a broken experience.

That's true, double notifications for sure must be annoying but why should we disable the notifications on the web application in this case? Isn't it a clear sign from the user that they want to try the web application if they installed it when they already had the native application installed?

> "Completely broken" is an overstatement. This proposal will stop just one thing from working, notifications (which you will already be getting to your native app). The other thing we would disable is the install prompt, which doesn't affect the installed-app experience.

I agree that it depends on the application. This said, it's probably very likely that if I installed one web application and the notifications are still fired on the native application, as a user, I will never use the web application as the engagement will go to the other one.

I'm also a bit worried about edge cases such as the native application being installed but technically not usable/used (not logged in, notifications disabled) which would lead to a weird experience.

More I think about it, more I think it will be hard to do the right thing auto-magically. Sounds like developers or users should deal with this as they are in control of the experience. Based on your initial comment, sounds like developers don't care as much as we hoped. Are users complaining about this? or are they finding solutions such as manually disabling notifications?

-- 
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/manifest/issues/658#issuecomment-372259720