discussions-and-proposals

Yes, but not for long. Src: https://github.com/react-native-community/discussions-and-pr...

Yeah, and according to https://expo.dev/blog/precompiled-react-native-for-ios and linked https://github.com/react-native-community/discussions-and-pr..., it seems moving off CocoaPods has barely moved past planning stage. Latest update from two weeks ago links to https://github.com/facebook/react-native/pull/52909 and says it’s very very experimental. Just great…

> Agreed with the article. Some will say just do iOS/Cordova/React Native/Flutter. But these have all the same problems eventually. I don't have enough experience with iOS. React Native, Cordova [and Flutter], however, as a different problem and that's that you need someone to deal with underlying platform changes, the libraries that you rely on adds another layer of leaky abstraction between your app and the Android platform. Now, you have to wait for someone to update the underlying libraries as well, for example, https://github.com/react-native-community/discussions-and-pr...

Using Catalyst is another option: https://github.com/react-native-community/discussions-and-pr...

Ah yea I haven't run into the state restoration thing. Fabric[0] is fairly exciting though, and seems like it will have a sync API. I think they've improved quite a bit on animations, the Animated library has worked well for me with PanResponder, I was able to get a pretty complex bottom drawer interaction working (much like Apple Maps) where you need to handle bubbling events with multiple nested scrollable areas and dragging that inits only when scrolled to top, etc, all came together very smoothly. In SwiftUI it was a similar API, but far more work to get to behave and in the end I was doing some hacky stuff to get it finally fully behaving. Granted, SwiftUI is early stage, so perhaps in a year or so it will also have figured all this out. As for testing, we've tested on a $100 two year old Android device with success, but nothing trul

Thanks for the comment - I wasn't aware of Catalyst, or that React Native is now actively integrating with it to support building native apps that run on iOS + macOS. Here's the most prominent issue I found that's tracking progress: https://github.com/react-native-community/discussions-and-pr... It does require macOS 10.15, so I imagine it will take time for the late majority and laggards (I am one) to catch up to the latest goodness. --- As much flak as Electron gets, I think it serves/served a purpose by opening up cross-platform app development to a wider audience, lowering the bar for better or worse. Commonly raised complaints about CPU/memory usage, file size, non-native UI, seem unavoidable due to the need of bundling Chromium. (Unless someone figures out a standard way to use a single shared install of the runtime.) With React Nat

There is a major re-architecture of React Native underway[1]. See Lorenzo Sciandra's excellent conference talk for an explanation of what the current limitations are in React Native and how they are planning on addressing them in the near future [2]. [1] https://github.com/react-native-community/discussions-and-pr... [2] https://www.youtube.com/watch?v=7gm0owyO8HU

It is no longer the case that Facebook is the only major contributor to React Native. Facebook and Microsoft now just started formalising their collaboration on the project with monthly(ish) meetings[0]. Other large companies like Twitter are using React Native Web (different than ReactJS) for their main progressive web app[1]. Other large companies using React Native are: - JD.com - Skype - Uber - Tesla - Discord You do have a point about _control_ of the React Native project though. That's still all with Facebook. The Github repo is currently setup as a mirror of part of the internal Facebook monorepo. Therefore, all pull requests need to be merged by a Facebook employee before it becomes part of "core". This is enough of a barrier that "non-core" part of React Native were split out so they could be managed and released independently[2]

react native + catalyst[1] would be best for you — to prepare for the future and be multi-platform, which is what we'll be releasing in my team[2] in the next few weeks. [1] https://github.com/react-native-community/discussions-and-pr... [2] https://standups.io