DEV Community


Discussion on: Breaking up with JavaScript

aop4 profile image
Andrew Puglionesi

Is native development "always better"? What if I'm a startup with limited resources and three developers that wants to reach everyone, regardless of their device?
Thanks for the criticism. I think the cross-platform approach will always be appealing to groups with fewer resources, but I agree that it's limited, especially when you want to do something that touches the operating system and the unique capabilities of a given platform. In my experience, it's actually a total pain in that case.
How about I rephrase it: some people happen to use JavaScript for mobile development, but if you wanna do Swift, go do Swift. He's right, you'll very likely find a job, and I shouldn't have painted anything like a black-and-white picture when there are plenty of people on both sides of the argument (and thus jobs for Swift people).

Thread Thread
antjanus profile image
Antonin Januska

I'm totally in agreement with you here. I work at a startup with constrained resources. We don't have a mobile app but we have been throwing around the idea of creating a desktop app where it's a similar conundrum: go native or use electron? And in the end, we have 6 JavaScript-y developers, customers with solid machines, and a web app as a primary focus.

Creating an electron app from a web app is a cinch and can easily be improved upon over time to deliver a better experience. Once we grow large enough, or the desktop app becomes a huge draw for new clients, we can dedicate time to native.

I imagine react-native faces something similar, though from what I've seen, RN is still a good option for most apps.