←back to thread

1192 points gniting | 6 comments | | HN request time: 0.002s | source | bottom
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 #
halper ◴[] No.43521802[source]
For me, there are a lot of applications that I want to be able to load regardless of whether I have a connection to the Internet or not: calendar, notes, mail etc. They can sync/send/whatever whenever I am next online.
replies(2): >>43521823 #>>43521901 #
1. turblety ◴[] No.43521823[source]
Ah yeah. While this is mostly implemented terrible, a web app can absolutely do this for you using service workers. So you can install a webapp to your homescreen and use it without an internet connection at all.
replies(3): >>43521906 #>>43521909 #>>43522643 #
2. wruza ◴[] No.43521906[source]
Emulate a network layer to serve a pre-packaged bundle. Neat "platform", but as a developer no thanks.

While apps are spying etc, making them is usually a no-brainer compared to churning and leaky web stacks. And probably not a single time a webapp loaded for me when I tried it outside standing in the wind trying to figure something out. It was always an app that started and helped and didn't ever scroll horizontally while doing so.

3. ablob ◴[] No.43521909[source]
In that case the only difference between a webapp and a normal app would be the permissions, wouldn't it?
replies(1): >>43522045 #
4. jspdown ◴[] No.43522045[source]
Permissions and performances.

But we could argue that if webapps were more used on mobiles, new APIs would have been opened to facilitate cross-app integrations.

5. sgt ◴[] No.43522643[source]
You seem to miss the fact that most web app experiences are inferior to that of native app.

The disadvantage of native is barrier to install. Once that's done, the experience to the user is simply superior. True native experience, fast and predictable. As a developer it's easier to build those types of apps as well.

People who haven't used iOS might not understand this though as they've never seen "how things should be".

replies(1): >>43541236 #
6. umbra07 ◴[] No.43541236[source]
you think most Android users are using PWAs instead of native apps? lol.