4 ms·
They didn’t use React Native, but wrote separate iOS and Android apps. Does this mean that React Native has lost support and investment from Meta?
by Yusefmosiah 3y ago
They didn’t use React Native, but wrote separate iOS and Android apps.
Does this mean that React Native has lost support and investment from Meta?
- drak0n1c 3y agoWith SwiftUI and Kotlin Jetpack Compose you can write architecturally and syntactically similar code across the two platforms. Essentially the same compact classes with the differences just being view property differences and OS API discrepancies (location, etc). So it's become a lot easier to manage separate development while keeping design direction and architecture on the same page. This is more so the case for apps with simple aesthetics and simple user interactions like Threads. It's not necessarily a sign that they are dropping support for React Native.
- rollcat 3y agoWell put. I intended to reply with something like "keep simple things simple" but you gave it much more depth.
- KaiserPro 3y agoIt means you get many more promotion points for creating a new framework and shipping it in a new product. Also, generally internal tools are exceedingly poorly documented and supported so it seems easier to write your things from scratch.
- JimDabell 3y agoAs the article states, they reused a tonne of things from Instagram.
- jamil7 3y agoI don’t think they’ve ever really built entire apps in React Native outside of maybe messenger? Usually a few screens are implemented in it and the rest native. Or maybe features are prototyped in it and later rewritten.
- moneil971 3y agoThey actually did another article with some good history on the iOS app for Facebook: https://engineering.fb.com/2023/02/06/ios/facebook-ios-app-architecture/ https://engineering.fb.com/2023/02/06/ios/facebook-ios-app-a...