Today I was using Jira and had to wait for the text in what should be a static dropdown menu to populate. It sat there with a bunch of placeholder boxes for a good 30 seconds. This has never happened to me with a native app.
al_borland
There's nothing like having a locally installed program that has no internet dependencies for reliability. There's a reason machine shops still have that one PC running MS-DOS 5.0 in an emulator. The tool built in Tk!Solver version 1 in 1982 can't be easily replaced, and it's required to compute bevel gear generator setups.
Changing anything in the setup might cause gears to come out wrong, and cost thousands of dollars in scrap, and the loss of a customer.
When you have a locally installed program, offline, you're pretty much immune to most of the troubles of the technical world.
mikewarot
For most apps, cross platform like Flutter or RN is the best choice. For apps highly bind on the hardware, or need better performance, usually native is better. But for vibe coding or harness coding today, if workload is not the problem, native is usually a better choice, it allows you do different thing on different platform.
linggen
On macOS and iOS, I prefer native apps because Apple gives these apps a bunch of extras in terms of keyboard shortcuts and functionality.
Non-native apps that are web views don't get this functionality unless the developer properly hooks it or mimics it. They rarely get this right.
That said, I'm not sure of the current state of Flutter and RN. They resolve to OS native controls, so theoretically they should support these types of base functionalities, correct?
runjake
For users, ease of use.
For companies, ease of additional tracking.
It really isn't some _deep_ thing. Users like to be able to quickly access the content they want to consume. Companies want data. Apps fulfill both of these requirements.
Jeremy1026
Because human beings are irrational and want "apps". I have numerous examples of native apps that are just wrappers around the web app performing extremely well (massively increasing conversion rates, revenue, etc) over the existing PWA.
leros
You get access to more APIs specific to the native platform, the looks and feel is far better (I can easily see when an app isn't a native iOS app - e.g., Liquid Glass is awesome), and the tool ecosystem (e.g., Xcode is specifically built for Apple Apps).
ra0x3
IMHO, for Android and IOS, Flutter is solid enough to implement apps which are near native ones in terms of performance and "look & feel"
_barban_
Native apps are not needed unless you want want performance and need to extract all the juice your hardware offers. Only AAA video games come to mind.
comments (10)
al_borland
Changing anything in the setup might cause gears to come out wrong, and cost thousands of dollars in scrap, and the loss of a customer.
When you have a locally installed program, offline, you're pretty much immune to most of the troubles of the technical world.
mikewarot
linggen
Non-native apps that are web views don't get this functionality unless the developer properly hooks it or mimics it. They rarely get this right.
That said, I'm not sure of the current state of Flutter and RN. They resolve to OS native controls, so theoretically they should support these types of base functionalities, correct?
runjake
For companies, ease of additional tracking.
It really isn't some _deep_ thing. Users like to be able to quickly access the content they want to consume. Companies want data. Apps fulfill both of these requirements.
Jeremy1026
leros
ra0x3
_barban_
farseer
mrdependable