this post was submitted on 02 Oct 2025
1574 points (98.9% liked)
Technology
75768 readers
2074 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Wait, where are you seeing a difference between that and how an app functions? Right now it feels like you're abstracting a bit too far in order to make a point, but I'm (genuinely) deeply curious what you mean.
Most apps are a packaged browser that makes proprietary API calls over https. However there is nothing proprietary or valuable in the app itself, except possibly some key material for authentication of the app with the back-end.
Then depending on the user making various requests a middle-ware program will interact with the backend database and retrieve the results back to the user. The database is the valuable part and other then the specific query the user is making, nothing else is can be retrieved by the user. Normally the middle ware isn't even downloadable either.
That's how everything (edit: that doesn't benefit from locally hosted resources, which have exceptions for things like gaming where rapid data access is more important than structural niceties) works, its a design paradigm called MVVM. Host the database, shift processing to the user's hardware (excepting hardware dependent tasks like LLMs or other compute heavy tasks). Websites, apps, even firmware -- essentially anything that makes an API call in some way uses this basic structure. Even entirely local applications do it this way (albeit internally).
Yes. Hence my initial claim that apps are worthless, and shouldn't be used if you can use a website instead. So the whole idea of Apple or Android being able to remove the "iceblock" app, shows that the app was ill-conceived to begin with. Or possibly it was even a honey-pot since apps do have much greater access to the parent device then a website.
I'm not disagreeing at all that this should have had a website as a backup, but you yourself are making some really good points about how apps aren't the same thing as websites and the benefits to using an app in this situation. Leveraging user hardware without the intermediate layer of a brower's sandbox is good for performance and makes a site much more robust in the face of things like DDOS, and having locally-hosted resources with which the user can interact without requiring an active TCP connection (because for example: ICE has geoblocked connectivity at one of their "enforcement actions" - but you can still document what's happening and the app will automatically-and-without-user-interaction upload what you've given it once connectivity is restored) is an incredibly important feature.
Offline websites, while potentially able to exhibit similar behavior, rely on extremely hacky workarounds and cached data to be able to do it - and an app is a much less volatile way to store that data than relying on your browser's cache reintegration (which will often be dumped if you're hit with bad a DHCP config).
I think your spirit is in the right place, but you're missing enough of the technical nuance that it's really undermining your ability to convincingly make your point. And again, I 100% agree that not having alternative access to this service is a critical loss.