Build a multiple-page application using React Navigation as follows.

1. Build the two-page application specified in these early sections of the React Navigation tutorial.
   • “Getting starting” — Create a new Expo application (cf. lab 1) and install React Navigation as explained here.
   • “Hello React Navigation” — Do this section as written. Be sure to install all the required libraries: @react-navigation/native; @react-navigation/native-stack; react-native-screens; react-native-safe-area-context.
   • “Moving between screens” — Do this section as written.
   • “Passing parameters to routes” — Do only the first section here, stopping before “Updating params”.

   When the tutorial application is running, create a text file (README.md) in the root of your lab directory that documents the application and includes one-sentence or one-phrase answers to the following:

   1. What React construct is used to implement separate pages of an application (cf. separate webpages on the Web)?
   2. What is the React Navigation concept that is analogous to a URL/URI on the Web?
   3. The onPress event handler for the home screen component is specified as () => navigation.navigate('Details'). Can we just say navigation.navigate('Details')? Why or why not?


2. Update the application to list some movies and provide details for them using the new implementations of the screen components found here.

   When the updated application is running, add one-sentence or one-phrase answers to the following to the README.md:

   4. Explain how the hard-coded movie list is presented as a list of titles on the homepage.
   5. Explain how the details screen presents the details of a single movie.

Submit this application by pushing it to your cs262 repo.

Make sure that your stakeholders have access to your team materials.

• They should already have access to your (public) GitHub repos.
• Create a #stakeholders channel in your team’s Slack workspace, in which your stakeholders can post their comments for the homeworks. You can choose which of your channels they have access to, but they should have access to #stakeholders and they should not have access to #grading.

Participate in the following two meetings:

• as a team member in your team’s meeting with its stakeholders
• as a stakeholder in your monitored team’s meeting

Each project team should have one team member give a one-minute project-pitch presentation to us and their stakeholders.

Meet with your teammates to write user stories for your project. Focus on completing the stories required for this sprint.