Netty vs React Native: What are the differences?
Netty belongs to "Concurrency Frameworks" category of the tech stack, while React Native can be primarily classified under "Cross-Platform Mobile Development".
"High Performance" is the primary reason why developers consider Netty over the competitors, whereas "Learn once write everywhere" was stated as the key factor in picking React Native.
Netty and React Native are both open source tools. It seems that React Native with 78.3K GitHub stars and 17.5K forks on GitHub has more adoption than Netty with 19.7K GitHub stars and 8.92K GitHub forks.
According to the StackShare community, React Native has a broader approval, being mentioned in 701 company stacks & 782 developers stacks; compared to Netty, which is listed in 11 company stacks and 14 developer stacks.
What is Netty?
What is React Native?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Netty?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Netty?
Sign up to get full access to all the tool integrationsMake informed product decisions
For a front end dev like me, using a mobile framework for side projects makes more sense than writing a native app. I had used Apache Cordova (formerly PhoneGap) before (because React Native didn't exist yet), and was happy with it. But once React Native came out, it made more sense to go that way instead. It's more efficient and smooth, since it doesn't have the simulation overhead, and has more access to hardware features. It feels cleaner since you don't need to deal with #WebView, using native UI widgets directly. I also considered Flutter . It looks promising, but is relatively new to the game, and React Native seems more stable for now.
I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.
The Expo SDK also provides convenient features like Facebook login,
MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/
The capability of style customization is one a large deal breaker for frontend SDKs. To solve this, we decided to use styled-components in our SDK, which makes it easy to add support for themes on top of our existing components. This practice reduces the maintenance effort for stylings of custom components and keeps the overall codebase clean.
I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
React Native is great in that it reduces the overhead of writing native code based on a web app. If written in a good style, Redux part of the app can often just be copied or shared in the Native app - and it just works! What a timesaver.
The framework used to write the mobile apps in this project. I've chosen this because of the "write once run all" (ios and android) mentality.
We are not currently using this product but we have very high interest in learning and using this for mobile apps.
New features of our app are developed on React Native, so we could maintain a small dev team.