Common Pitfalls in React Native Apps and How to fix them
summary
Practical failures and fixes: importing Expo Google fonts naively bloats a bundle to ~150 MB and crashes some Android phones, so import the exact font file; saving auth tokens in localStorage fails on devices — use react native async storage and JSON stringify/parse; HTML article strings require a renderer like render HTML to map tags to native Text/Image; conditional rendering must use booleans to avoid zeros or runtime crashes on real phones.
AI-written summary · about
chapters (6)
- 0:00React Native pitfalls intro
- 2:16Default fonts crash
- 4:45Local storage limits
- 6:51HTML in React Native
- 8:16Numbers vs booleans in render
- 9:21Key takeaways
related talks
44mReact Native: how to succeed with your mobile app
39mFrom React to React Native
25mReact Native in Practice
26mContributing To React Native Is Easy
11mTips for Building Successful React Native Apps
42mHow to publish a React Native component library
26mOptimizing React Native Performance
31mFrom React to Native
