Native Apps Why?
11–20 of 27 posts
Re: Native Apps Why?
#12Re: Native Apps Why?
#13Changing 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.
Re: Native Apps Why?
#14Native 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.
Surely that was a rushed reply(?). How about regular system utilities? Video/audio editors? IDE's? Debuggers? Image/3D editors? Compressor/decompressors? Terminal emulators? And so much more stuff.
Sure, many of these already have "web" versions but there's still a lot of apps that benefit greatly from being native and not go through another browser/webview/node instance.
Re: Native Apps Why?
#15Re: Native Apps Why?
#16Re: Native Apps Why?
#17If the app needs connectivity for data, and is just text/images/video, then yes, it should be a web app. e.g. news sites, social media, forums, etc. (It's a site, not an app).
If an app needs be able to work offline, on local files and data, then it should be native. e.g. office apps, image/video editors, maps, CAD, etc.
There's a grey area in between, but usually it's pretty obvious.
Re: Native Apps Why?
#18On 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…
I have built an application that I originally intended to be a PWA, but I had to make it a native application because how Apple are limiting many things for me.
It sucks because I now have to pay the apple tax and get "accepted" by Apple. Ironic, considering the original release of the iPhone, where web apps where the promise to us.
Re: Native Apps Why?
#19Native 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.
Come on, you really only see AAA video games requiring native apps? Surely that was a rushed reply(?). How about regular system utilities? Video/audio editors? IDE's? Debuggers? Image/3D editors? Compressor/decompressors? Terminal emulators? And so much more stuff. Sure, many of these already have "web" versions but there's still a lot of apps that benefit greatly from being native and not go through another browser/…
> Video/audio editors? IDE's? Debuggers? Image/3D editors? Compressor/decompressors? Terminal emulators? And so much more stuff.
Video I can understand, and anything that needs a real local terminal. On the other hand, audio, IDEs and debuggers, image editors, 3D editors, codecs, and remote terminals, nah.
My first use of most of those things was on a Performa 5200 whose CPU registers had lower bandwidth (though obviously better latency) than my phone's cellular 4G modem.
Web stuff may feels un-performant, but a lot of this is due to a mix of a thousand or so analytics libraries all competing with each other to spy on everything you do, plus some kind of reactive nonsense that isn't half as good as it wants the developers to think it is, plus zero incentive from the companies to the coders to make things fast.