zlacker

[return to "Do not download the app, use the website"]
1. rustys+Fg[view] [source] 2025-07-26 00:19:04
>>foxfir+(OP)
I cannot agree more and this has always been a pet peeve of mine.

Most native apps are some half gig large where even the heaviest website is a few mb. They dont let you highlight text and have other bizarre design choices. Even worse, they request importing contacts list which isnt even an option on the web.

Native apps could be butter but more often than not they are like margarine. Smooth, oily, and not good for you.

◧◩
2. ljm+tp[view] [source] 2025-07-26 01:58:28
>>rustys+Fg
A lot of native apps are just wrappers around a JS context with a few bridges into native APIs and they are pure data grabs.

Reddit always asks you to use its native app, for example. Why the fuck would I care so much about Reddit that I want it outside of my browser? Same goes for any other website.

◧◩◪
3. spauld+hq[view] [source] 2025-07-26 02:08:42
>>ljm+tp
Reddit is one of the cases where a native app makes sense. Some of the 3rd party Reddit apps were great.

But I'll eat my hat before I'll install Reddit's own app. Reddit killing off 3rd party apps is why I post here and not there.

◧◩◪◨
4. Gigach+5t[view] [source] 2025-07-26 02:42:59
>>spauld+hq
How does an app for Reddit make sense? It’s an image and text platform. There’s no weird hardware apis required.

Native apps make sense when you need to tap in to platform specific features like the Lidar api and such. They don’t make any sense for most websites.

◧◩◪◨⬒
5. craftk+yx[view] [source] 2025-07-26 03:42:33
>>Gigach+5t
They would seamlessly in the background pre-cache all the articles and images coming up in your feed so if you had intermittent connections like on the subway, you could browse nearly[0] unaffected.

[0] Unfortunately, the app I used in the before-time did not implement queuing for submitting comments/posts so that functionality was broken while you were between stations, and videos weren't cached.

◧◩◪◨⬒⬓
6. Daniel+Zx[view] [source] 2025-07-26 03:52:13
>>craftk+yx
Web apps can do that too with service workers, it is just a bit of a pain in the ass.
◧◩◪◨⬒⬓⬔
7. progva+YI[view] [source] 2025-07-26 06:23:33
>>Daniel+Zx
And if you ever push a service worker with a bug, then you make the browser permanently unable to display the site unless the user knows how to manually remove the service worker. I've seen it happen on Gmail.
◧◩◪◨⬒⬓⬔⧯
8. Daniel+yp4[view] [source] 2025-07-28 00:31:45
>>progva+YI
Yes it is a pain in the ass, but just for other people who read this, the bug was in the self-update code for the service worker. If you mess up the cache configuration it can make the service worker never look for an updated version of itself.

It is quite subtle thing in a very small part of the service-worker code but it is not like any random update can brick your app.

[go to top]