WE THOUGHT REACT NATIVE WAS THE ANSWER — UNTIL OUR APP HIT 190% CPU

Summary from the TLDR Web Dev newsletter

Motion initially chose React Native for its mobile app to use its JavaScript team and share code across platforms, but ran into performance issues when its calendar screen hit 190% CPU usage due to the overhead of bridging between JavaScript and native code. After trying various optimization techniques like caching and lazy loading that only provided marginal improvements, its team rewrote the calendar screen in native code, which reduced CPU usage to just 5%. The company now follows a hybrid approach where new features are built in React Native first for speed, then converted to native code based on performance demands.