1. What's the main difference between navigation in React web apps and React Native apps?
   1. There is no meaningful difference between web and mobile applications in terms of navigation.
   2. Web applications rely on URLs as the central concept for moving around. Native apps have no such concept, so it's up to the developer and the navigation libs they use to manage their screens.
   3. Native application code uses URLs the same way as with web applications, but these just aren't exposed to the user.
2. What function should be used to navigate to a new screen?
   1. Screen components are passed a navigation property. You should use navigation.navigate() to move to another screen.
   2. The screen component automatically has navigation methods added to it.
   3. There's a global navigation object that has navigation methods that you can use.

3. Does react-navigation handle back button functionality for you?
   1. Yes. Including the built-in back button on Android systems.
   2. No, you have to implement all back button behavior yourself.
4. How do you pass data to screens?
   1. You can pass a plain object as the second argument to navigation.navigate(). The properties are then accessible to the screen via navigation.getParam().
   2. You have to re-render the screen component, passing it parameters that you get as properties from navigation.
   3. You don't pass data to screens. Setting application level state is the only way to get data into screen components.