Currently, the application's navigation is a mess. Update it using four branches from the root - authorization and application for the patient and authorization and application for standby. Parameters for determining which will be which already exist in the redux state. Use switch navigation between authorization and application and stack navigation within them (see React Navigation, n.d.). For a good introduction, see the section, "Understanding navigation", by Idris (2017).
This will also require separating old components into more new ones. For example, the view where standby users are asked to enter the e-mail address of their patient should be separated into its own component, remaining within the standby-application branch. This will enable standby users to go back via the header if they mistakenly enter the wrong e-mail.
Currently, the application's navigation is a mess. Update it using four branches from the root - authorization and application for the patient and authorization and application for standby. Parameters for determining which will be which already exist in the redux state. Use switch navigation between authorization and application and stack navigation within them (see React Navigation, n.d.). For a good introduction, see the section, "Understanding navigation", by Idris (2017).
This will also require separating old components into more new ones. For example, the view where standby users are asked to enter the e-mail address of their patient should be separated into its own component, remaining within the standby-application branch. This will enable standby users to go back via the header if they mistakenly enter the wrong e-mail.
Reference:
Idris, N. (2017, April 15). Navigation and styling with React Native [Blog post]. Retrieved from https://developerlife.com/2017/04/15/navigation-and-styling-with-react-native/
React Navigation [Documentation]. (n.d.). https://reactnavigation.org/docs/en/getting-started.html