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

It might be interesting to have this implemented as implementation details before being spec'd. However, there are some issues that are still worth thinking of and may not be solved by dropping the spec changes. The two proposals are suggesting that native applications should take precedence over web applications. For example, it would mean that installing Twitter Lite will never send a notification if Twitter is installed. In general, I'm worried about the Web Platform putting other platforms first but it may also be a very surprising behaviour for a user. Trying a web application (if they can install it) will sound completely broken because they already had the native application installed and might not realise it. There are also various privacy issues as these behaviour changes could be detected by the website and they would be able to more easily track users and know more about them.

Though, I think having Chrome look into those problems independently from the specification process would be interesting.

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