It's not just about the size; it's also about execution time, runtime memory usage, and load. Native Java or Kotlin generally performs more efficiently compared to Flutter or JavaScript. Unlike Flutter and JavaScript, which require runtime interpretation and compilation, Java and Kotlin code is compiled directly at build time. Additionally, JavaScript and Flutter often make unnecessary system calls to convert runtime execution into platform-native code, as they rely on interpreters and do not execute directly on the system.
For multithreaded behavior on Android, Java and Kotlin apps typically offer better performance, as they support built-in multithreading capabilities. You can use libraries like RxJava to create non-blocking pipelines. Starting with Android 14 and above, you can also use Reactor, which is optimized for better performance and efficiency compared to RxJava, modern design and improvements in handling asynchronous and reactive tasks. If you don't believe me, try opening some streaming apps built on React Native, and you'll notice your phone heating up and draining a lot of battery within just a few minutes. This happens because React Native apps rely on a JavaScript bridge to communicate with native components, which can introduce performance overhead, leading to higher CPU usage, increased battery consumption, and more heat compared to apps built natively with Java or Kotlin.
Hi I couldn't understand Hindi. I assumed you were saying Expo and react native is different right? I will try with simple React native and if there's any major change I'll post a video about it
Bro as you see in his video he talked in good ways and politely you should also do that, and yeah your point valid he should compare bare react native app build but I think it's not his mistake, react native made the docs like that everyone start with expo and now they also hide or you can say made hard to find bare react native installation even now on started bare react native template also removed from rn cli
