I would argue that people want a certain quality experience. They don't care about whether the developer used Swift or Javascript or OCaml to deliver it.
The Web does usually deliver a certain baseline experience, and most platforms actually deliver a browser which mostly matches platform experience.
For native apps, there is a wide variety of things which you may or may not be able to do based on what the developers implemented and whatever their chosen toolkit supports - including toolkits which reimplement their own drawing, widget and event systems and does not support accessibility or even consistent copy/paste.
For web apps, you do have to somewhat actively have to break this stuff as a developer.
I would argue that people want a certain quality experience. They don't care about whether the developer used Swift or Javascript or OCaml to deliver it.
The Web does usually deliver a certain baseline experience, and most platforms actually deliver a browser which mostly matches platform experience.
For native apps, there is a wide variety of things which you may or may not be able to do based on what the developers implemented and whatever their chosen toolkit supports - including toolkits which reimplement their own drawing, widget and event systems and does not support accessibility or even consistent copy/paste.
For web apps, you do have to somewhat actively have to break this stuff as a developer.