←back to thread

1192 points gniting | 6 comments | | HN request time: 0.001s | 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 #
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. divan ◴[] No.43524128[source]
> browser apps do have their advantages:

These are more like byproduct of the fact that web apps are built on the stack not suited for modern UI apps. It's literally a text typesetting engine pretending to be a rendering engine for high-performance UI.

So, it can also be framed as:

- everything is selectable, even what shouldn't be - buttons, drawers, video players, etc - content is zoomable, which most of the time just breaks UX in hilariuous ways. Developers have to do extra-work to either disable zoom or make hacks/workarounds.

"Everything is selectable" and "everything is zoomable" makes total sense if it's a blog post. If it's a UI for the modern app, it does not.

replies(3): >>43525741 #>>43526201 #>>43536551 #
2. rblatz ◴[] No.43525741[source]
Disabling zoom is so hostile, why not disable screen readers and put bollards on handicapped ramps while you are at it. It’s literally a middle finger to older people and people with vision issues. If you disable zoom I will not be using your website.
replies(1): >>43526756 #
3. mvdtnz ◴[] No.43526201[source]
> It's literally a text typesetting engine pretending to be a rendering engine for high-performance UI

This is an outdated view of the web. Catch up or be left behind.

replies(1): >>43526746 #
4. divan ◴[] No.43526746[source]
This is factual view. No matter how many layers of abstraction you put on top, the foundation is always there. Luckily we have better and better support for wasm in browsers, so it's a matter of time when this outdated stack will be replaced with solutions designed from the ground up for the task.
5. divan ◴[] No.43526756[source]
Luckly most popular operating systems have concept of global text size that can be adjusted, and non-web UI frameworks respect that.
6. nsonha ◴[] No.43536551[source]
Web just have defaults that are not suitable for apps. Disable text select is one line of css, not that hard.