[Discussion] React Native Controllers Evolution #87
Description
During the last few months we’ve been hard at work on a native navigation solution for Android. Working on both platforms in parallel introduced new challenges and helped us better understand how this entire project should be split up.
We’re currently thinking about merging react-native-controllers into react-native-navigation. This will make the codebase much simpler and unify the API between iOS and Android, while maintaining the native differences in UX between the two platforms.
This will naturally be a major version that will break some API’s that no longer make sense. In addition, there are many major features (like Screen lifecycle - onAppear, onDisappear events) that we held off until we figure out how Android fits into things. Introducing these features will require significant architecture changes, and doing these with Android around the corner did not make sense. All of these missing major features will now enter active development as the new architecture is finalized, along with all issues and pull requests.
We’d love to hear your feedback about evolving this library to the next level correctly. If you have ideas, questions or concerns please add them to the discussion in this issue.