←back to thread

1192 points gniting | 5 comments | | HN request time: 0.001s | 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 #
mojuba ◴[] No.43522355[source]
To be fair, browser apps do have their advantages:

- text is selectable

- content is zoomable

- you can have an ad/nuisance blocker

- page source is open

While native apps have their own advantages:

- much smoother experience esp. navigation, scrolling, animations, etc.

- better overall performance (JavaScript will always lose to the native binary)

- access to hardware opens new possibilities; audio, video accelerators etc.; there's a ton of things you can't do in the browser with audio for example

- widgets, some of them are nice and useful too

- for publishers: an app icon on the home screen is a reminder, a "hook" of sorts; this is the main reason they push apps over web versions

replies(3): >>43522702 #>>43524128 #>>43529798 #
1. blacklight ◴[] No.43522702{3}[source]
All the features you mentioned can also be achieved by a well developed PWA. Of course, minus the widgets or some deeper system integration (like controlling phone calls etc.)
replies(1): >>43523497 #
2. mojuba ◴[] No.43523497[source]
Try to build a more or less serious music synth in the browser that won’t kill your battery.
replies(2): >>43523526 #>>43560028 #
3. firtoz ◴[] No.43523526[source]
Heh, I was actually building one. Haven't considered the battery... Are the web audio APIs bad, or are you forced to use the CPU? I guess with webgpu it may be easier?
replies(1): >>43523870 #
4. mojuba ◴[] No.43523870{3}[source]
I think on iOS you need access on the CoreAudio level if you want to be efficient, ie fill audio buffers on a high priority thread with some lower level static language.
5. blacklight ◴[] No.43560028[source]
Of course, I'm not saying that one size fits all.

There are cases like media apps, camera apps, videogames, terminal emulators, clipboard managers etc. that won't become Web apps any time soon.

Either because they need to operate closer to the OS, or for performance expectation reasons.

But I've just had a quick scroll through the apps on my phone, and I can confidently say that 90% of them are basically HTTP clients that interact with an HTTP server.

And even those that do more could probably be wrapped into a WebAssembly artifact with comparable performance in a near future.

The reason why they are not PWAs, and why engineers are often expected to do triple work (iOS, Android, Web), and why there aren't more products released as PWAs, keeps eluding me.

Sure, you have to tell folks how the "Install/Add to home screen" process works from a mobile browser, but is it that really that much more friction compared to an App Store paradigm to justify the abuse of native apps that either reinvent the wheel multiple times, or are just unglorified Web browsers running an Electron app just to show you the discounts at the supermarket near your house?