3 ms·

As a user I don't want a React app. I want a native app. I can understand why you as a developer don't have time to maintain the different platforms, but for a

by sgt 7y ago

As a user I don't want a React app. I want a native app. I can understand why you as a developer don't have time to maintain the different platforms, but for a UI app running on my laptop or desktop I care about one platform and that is macOS. It's okay if it's Mac only and many apps are.

scarejunba 7y ago
Yeah, but let's be honest. Most users don't want a specific app. They want functionality. They'll pay for functionality in a React App while eschewing a native app without the functionality. The practice of this means solving the problem the fastest is the most important part. And if someone can rapidly build a native app so be it, but if they can only rapidly build React apps that's what they should do. Or they can do otherwise and they'll learn.
- franga2000 7y ago
  > Yeah, but let's be honest. Most users don't want a specific app. They want functionality True, but they also want to be able to run it without bringing their crappy laptop to a crawl. Devs excuse their inefficient code with "modern hardware is fast enough", but it ceases to be fast enough when the majority of your apps are inefficient. Try running Slack, Discord, Skype, Spotify and a couple Chrome tabs on a last-gen laptop. And now try to run something actually useful (Office, a game, whatever). You can't. I've seen completely non-technical users say "ugh, another web app". Alternatives are few, so users won't use something else, true, but that's not an excuse to keep making inefficient apps. (I realize this doesn't apply nearly as much to React Native, but only React was mentioned above and this is a rant I've had prepared for a while now...)
ex3ndr 7y ago
React app is a native app. JS performance is ~the same in UI part - just declare what you want to display and native part will do the rest. It is much much easier to write slow AppKit code than RN one. Actually it is really hard to achieve decent performance with AppKit.

by sgt 7y ago

scarejunba 7y ago

Yeah, but let's be honest. Most users don't want a specific app. They want functionality. They'll pay for functionality in a React App while eschewing a native app without the functionality. The practice of this means solving the problem the fastest is the most important part. And if someone can rapidly build a native app so be it, but if they can only rapidly build React apps that's what they should do. Or they can do otherwise and they'll learn.

franga2000 7y ago
> Yeah, but let's be honest. Most users don't want a specific app. They want functionality True, but they also want to be able to run it without bringing their crappy laptop to a crawl. Devs excuse their inefficient code with "modern hardware is fast enough", but it ceases to be fast enough when the majority of your apps are inefficient. Try running Slack, Discord, Skype, Spotify and a couple Chrome tabs on a last-gen laptop. And now try to run something actually useful (Office, a game, whatever). You can't. I've seen completely non-technical users say "ugh, another web app". Alternatives are few, so users won't use something else, true, but that's not an excuse to keep making inefficient apps. (I realize this doesn't apply nearly as much to React Native, but only React was mentioned above and this is a rant I've had prepared for a while now...)

ex3ndr 7y ago

React app is a native app. JS performance is ~the same in UI part - just declare what you want to display and native part will do the rest. It is much much easier to write slow AppKit code than RN one. Actually it is really hard to achieve decent performance with AppKit.