Thread by @WildCat_io

Why you may want to use #ReactNative in 2022. A thread.

Pros:
- Lots of big companies use it and provide great experiences: Microsoft, Tesla, Discord (excellent), Shopify
- Active community

- Atwood's Law: "Any application that can be written in JavaScript, will eventually be written in JavaScript."
- React's state management framework is still a million years ahead of SwiftUI/UIKit. Recently I tried #zustand recommended by @GeekPlux.

The more I used this framework, the more I regret how much time I've wasted on Apple's toy framework. Totally unnecessary.
- In scenarios where it doesn't fit, you can fall back to the system native solution

Cons:
- Adds a lot of compile time.

But can be solved with some hack like packaging React Native as xcframework.
- It is doubtful whether Meta (FB) will maintain it in the future. But this is not a problem that should be worried about for 5 years. This is also the benefit of open-source frameworks.

Compared to SwiftUI's iterations over the years, the advantages are particularly clear
- The community has a lot of badly manintained libs. But this is also a sign of an active community as well

Steve Jobs said, "You have to start with the customer experience and work backwards to the technology".

But seeing these #WWDC updates over the past few years, Apple's strategy now seems to be "you have to start with cooool SwiftUI framework and work backwards to the user experience" due to the lack of "backward compatibility".

SwiftUI/UIKit seems to be a big joke when it comes to improving the user experience compared to the Android's better backward compatibility system (developer.android.com/topic/librarie…).

Developers spend dozens of hours a year learning new Apple technologies. And then it can be three to five years before they are fully usable in production. And these new technologies would have bugs that can't be fixed in a timely manner.

I'll take "spot goods" over risky "futures".

(The end of this thread)