5 ms·

I totaly agree with you. What web-devs often forget is that native (mobile apps) have a very different runtime environments, things come and go (onCreate, onDes

by TeeWEE 11y ago

I totaly agree with you. What web-devs often forget is that native (mobile apps) have a very different runtime environments, things come and go (onCreate, onDestroy). Memory gets destroyed and reused. You need to think about background processes, multithreading. App startup is of upmost important. (starting a web page takes a lot of time, people every noticed that ios-chrome only has one page in memory at a single point ?). Its just a different mindset. The webbrowser is an abstraction on top of UI toolkits, with a very dynamic rendering engine, and simplified execution environment. Once you have a a hammer (javascript), it doesnt mean you should apply it everywhere.

Wintamute 11y ago
tl;dr React Native doesn't use browser. It's not clear from your comment whether you're familiar with React Native architecture or not. A React Native app works by using JS/React as the "brains" of the app (http services, state, smart components) and runs this in a separate thread to a 100% native portion of the app that uses uses platform specific native ui controls. Animation performance is pretty good because of this multithreaded approach. So in this way your JS app brain can be portable across platforms, while the nitty gritty view layer may shift to accommodate the capabilities of the native components you work with on each platform.