When comparing React Native vs B4X, the Slant community recommends B4X for most people. In the question“What are the best ways to make a cross-platform application?” B4X is ranked 2nd while React Native is ranked 10th.
Ranked in these QuestionsQuestion Ranking
Pro Allows you to develop native apps
Pro Backed by Facebook
Facebook writes their mobile apps in React Native so the code base gets pretty thoroughly used in some highly demanding scenarios.
Pro More predictable control of the state
The one way data flow, makes it more predictable and easy to control.
Pro A very active forum where you can find any issue you have, and quick answers to new ones
Pro Live code swapping
A huge productivity boost when you can run your apps on the devices and make code changes real time without needing to recompile.
Pro A highly motivated program author who is very active in the forums
Erel Uziel is simply the most pro-active Soft-Creator/Forum Manager you will ever come across. If it has not yet been asked & answered, just ask and you will be answered withing minutes, and thanks to it being a trully international forum, this is achieved 24h/7d.
Pro Very easy to use and powerful for IoT
Support for Bluetooth/BLE, MQTT, TCP/UDP, Serial, NFC, Websockets, HTTP/2 across platforms makes it the ideal tool for IoT projects.
Pro Create easy, fast and with less code cross-platform views
B4XUI custom views are designed, by Erel and other forum members, exactly with this in mind; custom views that act and feel exactly the same no matter what platform you target.
Pro Powerful general purpose programming tool
As mentioned in its website, "With B4X, anyone who wants to, can develop real-world solutions."
Pro No complexities compared with other tools
No need to learn JAVA, C+, PHP, or any other complementary languages in order to achieve exactly what you need.
Pro Many informative video tutorials
The tutorials help beginners as well as more experienced programmers grasping important concepts.
Pro The best tool with the best service by Erel
Con Steep learning curve
Con If core team doesn't use a certain feature, it's not developed
Whenever there's functionality you need that they don't use in their apps, it's not going to get developed by them, even if it's obvious it should be in the core. They always say to either submit a PR or create a separate module.