Everywhere: Bringing Into Native Apps

on YouTube ↗21m

" summary

Argues that swapping WebView for a React Native view removes the performance and integration bottlenecks by rendering real native UI, using Metro platform extensions (.native.tsx) to pick platform files, and bundling a full RN runtime + JS/assets into a single XCFramework/AAR artifact. Describes Callstack helpers (runtime initialization, navigation bridging) under the name React Native brownfield, cites Expo SDK and Nativewind for device APIs and styling, and reports smoother gestures, direct native access, and incremental migration working in practice.

AI-written summary · about

" chapters (9)

1. 0:00Introduction and web views
2. 3:04Understanding web view limits
3. 6:50Brownfield development
4. 10:00Tooling and packaging
5. 11:22Universal UI architecture
6. 15:53Platform API integration
7. 16:59Solving technical trade-offs
8. 18:10Strategic migration path
9. 19:26Conclusion and shifting focus

" related talks

• 53mHow React-Native shapes the way we think about native appsIlya Ivanov · Mobile Fest 2018
• 52mWhy you should use React Native for your next mobile appGwendolyn Faraday · NDC London 2018
• 45mAbout React Native inside your existing Android AppDamien Cavaillès · Android Makers 2017
• 27mBuilding high quality mobile apps with React NativeParashuram Narasimhan · State of platforms: Fragments Ahmedabad 2019
• 01h 01mReact Native: A Better Way to Do MobileBrent Vatne · Philly ETE 2016
• 33mReact NativeChen Feldman · ReactNext 2019
• 35mMigration Web (Angular) to Mobile Development (React Native)Artem Paliy · VinnytsiaJS 2018
• 20mDissolving Boundaries: The Fusion of React app and Native Apps!Ravi Raj Singh · CityJS New Delhi 2024