zlacker

>>gnitin+(OP)
I still, will never understand the need for native "Apps". To this day, I have never seen an "App" that couldn't simply have been a website/webapp. Most of them would likely be improved by being a webapp.

The only benefits I can see of "Apps", are the developer get's access to private information they really don't need.

Yeah, they get to be on the "App Store". But the "App Store" is a totally unnecessary concept introduced by Apple/Google so they could scrape a huge percentage in sales.

Web browsers have good (not perfect) sandboxing, costs no fees to "submit" and are accessible to everyone on every phone.

>>turble+KJ
Simple, UX.

The reality is, most webapps for mobile just suck. The UX is nowhere near that of a native application. I don't want any text to be selectable. I don't want pull to refresh on every page. I don't want the left-swipe to take me to the previous page.

You can probably find workarounds for all these issues. The new Silk library (https://silkhq.co/) is the first case I've seen that get's very close to a native experience. But even the fact that this is a paid library comes to show how non-trivial this is.

>>xxprog+tR
> I don't want any text to be selectable

Disabling text selection is not just worse UX, it is actively user-hostile

>>nodar8+wk1
I have literally never needed to select text in a UX element.

In the past, occasionally there would be an error message in a message box dialog that I wanted to copy and paste. And then I discovered that despite it not looking selectable, it actually was.

I don't want to accidentally select the text of my menu bar, or of a text box label, or a dialog tab title.

>>crazyg+9s1
I, I, I. Empathy is a weakness.

Lots of limitations for you to not accidentally do something, maybe there is a way to not accidentally do those things and also help people that need them.

>>sitkac+JQ1
No, not providing concrete examples is a weakness.

You're awfully arrogant in making a judgement about my empathy... if you want to make this personal.

Or maybe you can justify why people need to be able to select menu labels in the first place? That's not standard on any OS I've ever used, so it's up to the person who wants to change things to justify why.

Maybe be less judgmental of people here on HN, and contribute something factual instead? I at least gave a factual account of my personal experience, which is a data point. Describing one's experience isn't egoism.

>>crazyg+v22
A simple and concrete example is, go to Japan, find yourself in need of using any Japanese-only app, be extremely frustrated in not even being able to select text to translate it.

At least in recent versions of Android there is that OCR (?) powered functionality to select text when you're in switch-app view.

>>nazgul+Mk2
Circle to Search can translate everything on your screen without you needing to go through the whole "copy text, open Translate, paste, switch back to app" workflow. You just hold the home button, then press the translate button.