react-native-screens provides native primitives to represent screens instead of plain components in order to better take advantage of operating system behavior and optimizations around screens
However, there is a significant issue on Android that requires disabling state serialization. This may cause lost state, for example. The consensus is that this is a design limitation of
I suggest that a doc update would be good to both: 1) add more detail to the current documentation of the value of using react-native-screens (because “in order to better take advantage of operating system behavior and optimizations around screens” is vague), and 2) add a warning about the above known risk and tradeoff on Android (and is this Android-only?).
Link to the related docs page