> In an app, undoing that is pretty much impossible (or at least, above my pay grade).
In my experience it is above the average user's pay grade to work around it in a browser too. Even power users will probably give up if the usual ways don't work out (holding alt, browser extension, reader mode). The power-est of users might glimpse at the inspector, but they'll give up if the nodes are obfuscated.
All this to say that with things like Circle To Search or Apple's built-in screenshot OCR nowadays websites and apps are finally on a level playing field when it comes to anyone being able to circumvent text protection.
Google pixel devices have had this for years. It's one of the few things that keeps me glued to this platform.
Just push the button to go to the task switch view and as long as the window preview thumbnail isn't blanked out, I can just get the phone to OCR any part of the screen in real time.
"Apps" of this sort are absolutely "on the web", and generally use browser engines to display the content. The real distinction IMO is between using a locked-down mobile interface vs. a full browser on a computer with an OS and UI intended to let you have that control.
You can know. There is always telltale jank in web apps. And there are things that are basically impossible to do in web apps, like reliable camera integration.
In an app, undoing that is pretty much impossible (or at least, above my pay grade).
This is one of a million reasons why apps are so bad.