Curious to hear more about their deep dive into Native, Flutter and React Native as possible technology choices.
Hopefully, React Native is not a nosedive ;)
Building all of our new mobile apps using React Native
51–60 of 588 posts
Re: Building all of our new mobile apps using React Native
#52Hahaha ahaahah
gee what happens when Android Fuchsia hits oem devices this year? CES surprise coming..
Re: Building all of our new mobile apps using React Native
#53And 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.
The company I've been contracting for lasted just over a year on react native before heading back to native. Even though the product was still a prototype, we were spending way too much time updating libraries and trying to decipher all the breaking dependencies. Some easy, some very cryptic.
On a side note, I'm not a big fan of people shoehorning stateless web development patterns into application environments that support stateful development. The solutions appropriate for development inside a web page are often not helpful inside an application binary.
Re: Building all of our new mobile apps using React Native
#54Earlier quoted context omitted.
My first thought was the Airbnb article "React Native at Airbnb" https://medium.com/airbnb-engineering/react-native-at-airbnb...
I understand how examples like this stick in people's minds, however, just because one company decided not to move forward with a technology doesn't mean that all companies will do the same. Facebook has continued to use it, Microsoft has begun using it heavily, Twitter uses it on the web[0], Discord has been very happy with it -- and countless other examples. [0] https://github.com/necolas/react-native-web
[deleted]
Re: Building all of our new mobile apps using React Native
#55And 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.
I have not seen one good app for android that has been written in react native. Can anyone show me one that doesn't suck in performance?
Re: Building all of our new mobile apps using React Native
#56Honestly 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…
> What's missing until regular websites have parity with mobile apps in functionality?
Performance. But we're beginning to approach performance parity - not by the web becoming an faster, mind you, but by apps becoming slower. It used to be only cheap/poor-quality apps that felt like glorified web pages, but now even many high-profile apps are just parts of a web stack embedded into an app.
Re: Building all of our new mobile apps using React Native
#57And 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.
I have not seen one good app for android that has been written in react native. Can anyone show me one that doesn't suck in performance?
From my understanding, it does exist in popular Android apps, but usually for larger apps its used for only parts of the app and not the entire app.
Discord is an interesting case. They were using React Native for iOS and not Android. In their defense, this probably makes sense since substantial code sharing could be achieved between their desktop/web app and their iPhone app with this approach.
Re: Building all of our new mobile apps using React Native
#58Honestly 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.
Re: Building all of our new mobile apps using React Native
#59Anyone know where React Native stands in modern development - especially when compared to Flutter and the upcoming Compose. All the native frameworks are also React inspired. I personally love the work done by Airbnb for its Android MvRx framework. Again, React inspired
React and it's model are great. React Native on the other hand is leaky, heavy and you'll spend a bunch of time fiddling with packages, upgrading them, tracking down weird linking issues and ultimately writing some Objective-C / Java code to debug / glue / fix whatever native API you're dealing with. Thats only from my experience though. I would much rather the Compose / SwiftUI direction.
Re: Building all of our new mobile apps using React Native
#60Arguably 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…
1: "Great idea. Which version of Electron should we use?"