alt Hacker NewsMy experience might be the minority, but I have found that 95% of the time, when an app is available on both web and native mobile, the native mobile version is significantly better - usually not because it's a fantastic app or has more features, but rather because the web version is more buggy/slow/confusing.
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.
Replies
Whether or not the UX is better, from a security standpoint I choose the web version because of browser sandboxing unless I'm forced to use the app. If I'm forced to use the app, I probably choose not to use the service.
> when an app is available on both web and native mobile, the native mobile version is significantly better
Did you read the article? One of the author's main points is this is a deliberate result by vendors.
I've found that the apps often just entirely miss out features that are available in the web versions. That's why I don't have the GitHub app.
Yea, webapps (even PWAs) still can't compete with native apps when it comes to responsiveness, but I still don't know why. I've yet to see even a demo PWA that passes the "native turing test" where I can't tell whether it's a native app or not.
Even native apps that were built with cross-platform frameworks feel a bit "off" sometimes.