React Native Radio RNR 354 - React Native Screens with Krzysztof Magiera
Feb 27, 2026
Krzysztof Magiera, software engineer and co-founder of Software Mansion who built key React Native libraries, discusses react-native-screens and its origins as a fix for memory and resource issues. He explains screens as native primitives powering navigation UI. They cover the V5 rewrite for the new architecture, platform limits, and why the library stays separate from navigation frameworks.
AI Snips
Chapters
Transcript
Episode notes
Memory Bug Sparked Screens Creation
- Krzysztof Magiera built react-native-screens after debugging apps where stacked screens kept large resources like blurred background images and maps in memory.
- On native platforms Krzysztof noticed stacks free resources for offscreen screens, which inspired exposing native screen primitives to release memory.
Why Screens Is Separate From Navigation
- Screens separates low-level native primitives from higher-level navigation APIs so libraries like React Navigation can iterate independently.
- Krzysztof calls Screens "the most important library you'll never use directly" because it exposes platform surface area while letting routers supply different user-facing APIs.
Expose Full Native Surface In Primitives
- Expose the full native surface when building primitives so higher-level libraries can implement convenience APIs.
- Krzysztof recommends being verbose in primitives to avoid limiting platform-specific options that end users may need.