You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When talking about natively build navigators for React Native the main problem with them have been compatibility with Android when activity is destroyed. When I turn "Don't keep activities" to ON on Android and put my app on background the activity is destroyed right away. With this setting on and using wix's react-native-navigation it does not remember the route I was in. This will be major drawback for apps that are required to be used on background too.
The main benefit with the JS based routing is that you can put routes to redux store which is not destroyed on activity destroy and all my routes are on memory even when activity is destroyed.
So I would recommend you guys to keep "Don't keep activities" to ON mode all the time when developing this navigator. And maybe it will become defacto navigation library of RN! :)
The text was updated successfully, but these errors were encountered:
When talking about natively build navigators for React Native the main problem with them have been compatibility with Android when activity is destroyed. When I turn "Don't keep activities" to ON on Android and put my app on background the activity is destroyed right away. With this setting on and using wix's react-native-navigation it does not remember the route I was in. This will be major drawback for apps that are required to be used on background too.
The main benefit with the JS based routing is that you can put routes to redux store which is not destroyed on activity destroy and all my routes are on memory even when activity is destroyed.
So I would recommend you guys to keep "Don't keep activities" to ON mode all the time when developing this navigator. And maybe it will become defacto navigation library of RN! :)
The text was updated successfully, but these errors were encountered: