←back to thread

1192 points gniting | 3 comments | | HN request time: 0s | source
Show context
turblety ◴[] No.43521702[source]
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.

replies(44): >>43521722 #>>43521779 #>>43521783 #>>43521802 #>>43521900 #>>43521921 #>>43522003 #>>43522027 #>>43522043 #>>43522070 #>>43522073 #>>43522076 #>>43522148 #>>43522176 #>>43522181 #>>43522194 #>>43522290 #>>43522337 #>>43522341 #>>43522613 #>>43522683 #>>43522825 #>>43522873 #>>43522885 #>>43522925 #>>43522935 #>>43522989 #>>43523037 #>>43523210 #>>43523300 #>>43523681 #>>43524483 #>>43524766 #>>43524876 #>>43524878 #>>43525133 #>>43525355 #>>43525416 #>>43525604 #>>43525642 #>>43526098 #>>43526688 #>>43537641 #>>43550064 #
xxprogamerxy ◴[] No.43522181[source]
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.

replies(15): >>43522293 #>>43522316 #>>43522326 #>>43522355 #>>43522507 #>>43522547 #>>43522568 #>>43522587 #>>43522599 #>>43522696 #>>43523887 #>>43523982 #>>43525120 #>>43525256 #>>43531140 #
fauigerzigerk ◴[] No.43522599[source]
>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.

Strange. This inability to select any text has always felt like one of the most hostile things developers could ever do. It feels like pure vandalism.

Another thing that causes massive productivity degradation is not being able to keep multiple pages open so you can come back to some state. I cannot imagine how anyone could possibly use these apps for any serious work.

The UX of almost all native mobile apps is absolute crap. But it's not their nativeness that makes them crap. I'm not complaining about the idea of operating systems offering non-portable but high performance UI primitives that make use of OS facilities.

Many native desktop apps don't have these UX issues (at least not all of them at the same time). It's the mobile UX patterns, conventions and native UI frameworks that are causing this catastrophic state of affairs.

replies(6): >>43522834 #>>43523840 #>>43524507 #>>43524573 #>>43526428 #>>43541157 #
1. tshaddox ◴[] No.43524507{3}[source]
Also, if my memory serves, native MacOS apps by default support selecting most text that isn’t part of a clickable element like a button.
replies(1): >>43548105 #
2. OrangeMusic ◴[] No.43548105[source]
No, that's absolutely not the case, and it would be very odd and disturbing.
replies(1): >>43552852 #
3. golvok ◴[] No.43552852[source]
I think it's an accessibility option that also makes navigating with the tab key more useful.