61–70 of 599 posts
I have it the other way around. I want local first app. Don’t want everything in the cloud apps. Luckily there is choice :)
It’s a little tough these days. With AI and scraping, running an open webapp/website is now more expensive than ever before. My friends and I have launched a product in the last few months and decided to focus on mobile first and wait to develop a webapp simply because we couldn’t feel we could optimize the costs of open webapp while we have so few resources.
Then with ChatGPT he had to enshittify his website with all these cloudflare capture stuff, making the site leeesssssssss fun to use; when complaining he mailed me that AI scrapers are slashing his servers
Earlier quoted context omitted.
> some web UIs nowadays are so bad and the app so good that I'm not sure this always holds true. This is by design to force you install the app. Most of these days, I just treat it as a signal to neither use the app nor the website.
Reddit comes to mind. I have so many issues with their mobile website. The back button has been broken for years, comments will frequently just hang as loading indefinitely (only fixable with a hard refresh), videos will sometimes not be replayable, sometimes if you change the zoom on the page it will just hard refresh, etc. I'm not sure if it is intentional to push you to the mobile app, but I have to imagine the mo…
Whether I prefer an app to be web or native is purely based on the use case (I probably would choose native for a dozen use cases and web for the remaining one million use cases), but that's orthogonal to the fact of which one is actually better.
Edit: And to be clear, I'm not referring to cases where the web app is purposefully restricted or injected with dark patterns to drive users to native. Even if you ignore those cases, this pattern still stands in my experience. Though, that doesn't mean there is no indirect quality bias, e.g. more money spent on the native devs than the web devs.
While I sympathize with the author, and feel the same way, I think Apple/Google have some blame here. They make certain simple things only possible in the apps, because the APIs are not exposed via the web. Notifications is a big obvious one. Not sure if they've changed it since I last looked into it, but having an app installed was the only way to send a notification to someone for a long time.
Isnt there are similar feature in iOS browser as in Firefox these "desktop notifications" that some webpages request?
This also skips over with some hand waving that a lot of mobile app uses cases simply can’t be replicated with web sites. Take gps or smart home control as two easy of the top of my head example the author skipped too. Also the fact that people here would rather have their info stored in the cloud vs local on device is interesting.
I understand the user point of view, but some web UIs nowadays are so bad and the app so good that I'm not sure this always holds true. I do agree that this seems to be exception rather than the rule - so having both is actually nice IMHO.
> some web UIs nowadays are so bad and the app so good that I'm not sure this always holds true. This is by design to force you install the app. Most of these days, I just treat it as a signal to neither use the app nor the website.