JavaScript producing native interfaces.
WHAT IT IS
A framework building mobile applications with JavaScript or TypeScript, rendering actual native components.
WHAT DISTINGUISHES IT FROM FLUTTER
It uses the platform's own controls rather than drawing its own.
WHAT THAT PROVIDES
Native appearance and behaviour by default Platform conventions followed automatically Accessibility support from the platform
WHAT IT COSTS
Differences between platforms that must be accommodated Performance dependent on the bridge between JavaScript and native
WHAT THE NEWER ARCHITECTURE CHANGED
Direct synchronous communication with native code, replacing the asynchronous bridge that was the main performance constraint.
WHAT IT SUITS
Teams already skilled in React Applications sharing logic with a web product Products needing both platforms quickly
WHAT IT DOES NOT SUIT
Graphics-intensive applications Applications requiring deep platform integration throughout
WHAT TO CHECK
Whether the packages you need support the current architecture.
WHAT TO EXPECT
Native knowledge still required for configuration, debugging and some features.
