Nothing unreasonable or unsubstantiated. This is exactly what happened with app geolocking, privacy sandbox/topics, SafetyNet/Play Integrity API, etc. All of these are supposed to improve security and privacy and yet none of them are under the control of the user. Clearly implying that the user is the biggest security/privacy threat to them.
Which sites require those? How would that allow them to make more profit?
I literally said if they want people to visit anywhere they use a site and if not they lock down the experience with an app, and you said they lock down apps as 'proof' that they'd lock down web sites because somehow they are equal. Apps have never been about freedom. Starbucks doesn't want user choice and privacy when they ask you to download their app.
And I'm yet to see what business model it would work for. I'm going with 'none'.
> Which sites require those? How would that allow them to make more profit?
Practically every banking site (or more importantly banking apps). And a lot of weird cases like bus/train timings app, mobile operator apps, etc. You don't see that a lot with websites yet because the web isn't so severely constrained as mobile apps are. But the moment they appear, it will go the other way. One good example of this is AMP - which thankfully fizzled out for other reasons.
> And I'm yet to see what business model it would work for. I'm going with 'none'.
You can go with whatever you feel like. But the real world experience corroborates what the other commenter said. And one good reason for this is the corporate security culture. 'Our app isn't secure if it doesn't use the PIntegrity' type of argument. They'll all fall for it even if it's detrimental to their users.
Making a website less accessible doesn't make any sense. You've given an example of apps like before and you've yet to substantiate any points you made, maybe bank logins have a reason to be secure but that forum you go to doesn't, and wouldn't do this.
If they wanted to make it less accessible they could easily do that by forcing you to use newer browser versions which some boilerplate sites with frameworks do, from lack of expertise. No "safety" required. I'm not going off feeling, I'm going off facts. It will NEVER happen.
