Arguably the biggest concern with React Native is that it is controlled by a single entity, Facebook, and that they are not one of the leading mobile platforms who from a business perspective have strong incentives to ensure the future of their respective app eco systems. Facebook's incentives with React Native are somewhat unclear. This is a big, yet often unspoken, reason companies are vary of depending on React Na…
>>> Facebook's incentives with React Native are somewhat unclear I always figured this conversation happened: 1: "We have all these engineers who write javascript but users are switching to native apps. what do we do?" 2: "We could retrain them all." 1: "That would be expensive and time consuming." 2: "We could fire them all." 1: "Also expensive and time consuming." 2: "Wait, what if we made it so you could write nat…
Building all of our new mobile apps using React Native
71–80 of 588 posts
Re: Building all of our new mobile apps using React Native
#72Re: Building all of our new mobile apps using React Native
#73And in a couple of years, "Why we are moving away from React Native at Shopify". Not slamming React Native but the sensationalistic headline. Anyone with a bit of experience in software should know better than making this kind of silly proclamation about the future of your software stack.
It's much less exciting, however, to say "React Native Is What's Next at Shopify".
Re: Building all of our new mobile apps using React Native
#74Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
The fact that Facebook themselves will never be able to replace their native iOS and Android apps with RN implementations says it all imo.
Re: Building all of our new mobile apps using React Native
#75Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
It can't be overstated how many apps are absolutely dependent on working push notifications (all chat for example) and can't be replicated as websites. And that's not yet implemented for iOS so we're all at Apple's mercy until it is, which may never be.
Re: Building all of our new mobile apps using React Native
#76I build an app with React Native Web and we produce Android/iOS/web from the same code base with 3 developers.
No, it's not perfect. Yes, JS can be awkward and confusing. Yes, a truly native app built by expert platform-specific developers would be better.
But I'm able to ship this product with less than half the team size I would need for native development. JavaScript developers are cheap to hire, and they don't need to know any objc/swift/java/kotlin to build the product.
Our product is consistent, because it's the same code across platforms. The business people paying us to build the app are thrilled at how quickly we can turn around features.
We've been shipping this way for 2 years and I would strongly recommend it to everyone.
Also, before people jump in with "But RN is slow and bloated!", it's actually not. The performance is just as good as truly native and the binary is small. The real downside is having the app not feel native, but only developers seem to notice. Pragmatically, most apps are so bad that if your Android app has an iOS look-and-feel nobody seems to care.
Re: Building all of our new mobile apps using React Native
#77I know that there exists ClojureScript bindings to React-Native...does anyone here have any experience working with them?
Re: Building all of our new mobile apps using React Native
#78Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
It can't be overstated how many apps are absolutely dependent on working push notifications (all chat for example) and can't be replicated as websites. And that's not yet implemented for iOS so we're all at Apple's mercy until it is, which may never be.
Re: Building all of our new mobile apps using React Native
#79Honestly I think the future of mobile will just be... mobile websites. What's missing until regular websites have parity with mobile apps in functionality? - Accelerometer and all sensor support (some of these are already supported on various browsers on various OSes) - Background support - Bluetooth - WiFi - Better notifications - etc. Sure there will always be a need for native, but 99% of apps don't need any of th…
You're viewing it through the lens of a developer. The user wants the best experience. Because software costs 0$ to distribute, the best user experience will always win out. The future of all software is faster, better software. Websites are shitty, arcane technology - the opposite of the future.
I would like all of my applications to be sandboxed by a browser I have control over.
Re: Building all of our new mobile apps using React Native
#80And as an added bonus, Flutter is easier to reason about, has edit and continue, and is more performant.
Perhaps the use of Dart instead of Javascript was a deal killer though?