Do the following exercises for this homework.

1. 

   Build a to-do application. The to-do app is a classic application that has been implemented hundreds of times, on dozens of platforms (e.g., see the image to the right). We’ll accept any form of this application that’s built using our class development environment (i.e., Expo; ReactNative; TypeScript) and that allows the user to:

   • Create new to-do items, each to be shown on a to-do list (e.g., there are 3 tasks listed in the sample image).
   • Edit an item on the to-do list (e.g., the user is currently editing the text of the 2nd task on the list).
   • Check an item off the list (e.g., the first task on the list is checked off).
   • Delete items from the list (e.g., the user has just deleted a 4th, now unseen, task from the list).

   For this assignment, and all following homework assignments, we suggest that you use GitHub CoPilot/Chat to build the application (see Guide 1 for the IDE plugins that can support this work and Guide 3 for instructions on how to use it). Given that we haven’t done much work with Expo and ReactNative yet, you can violate best practice here by building a default app (see lab 1) and asking Copilot to update it to a full to-do application.

   Do all of this in a homework1/todo-app/ sub-directory. When you have the app running on your device, save a screen shot of your running application (homework1/screenshot.png), add a new readme file (homework1/README.md) that uses Markdown format (see Guide 3 for details GitHub Markdown), and does the following.

   1. Cite examples from your codebase of each of the following JavaScript/TypeScript/HTML/CSS elements, or explain why your app doesn’t need them (see Guide 2 for details).
      • Object
      • Anonymous function using arrow notation
      • Asynchronous programming
      • Modules
      • Some code element that demonstrates that your code is TypeScript rather than JavaScript.
      • Some CSS-like specification.

      For example, if we were asked cite an example of a control structure, we might say that the following selective control statement (i.e., if statement) adds a task to the task list if there is any input.

          if (inputText.trim()) {
              onAddTodo(inputText.trim());
              setInputText("");
          }

   2. Describe how effectively Copilot worked for you on this assignment. What did it do correctly? incorrectly?

   Submit this application by pushing it to your cs262 repo (under homework1/).

2. Use the "Stakeholders" wiki in Moodle to sign up to be a stakeholder for one of the other project teams (cf. Guide 4). You will follow this team for the remainder of the semester so, as much as possible, we’d like to have only one member from each team reviewing any other team. Sign up for your team in Moodle under “Team Stakeholders”. When you’ve picked your team, review the sprint-one deliverables from the other team you are reviewing (see project deliverable #1 — see the team GitHub repo linked from the Moodle “Team Members” page) and post the following to their Slack #stakeholders channel:

   1. A one-paragraph review of their vision statement — How unique and compelling is their project idea? Is the vision statement well-written?
   2. A one-paragraph review of their prototype code — Is it there? Is it well-documented? Did they implement something reasonable on which to base their application?

   Be prepared to explain your review to them during their team meeting in lab 4.

   You may need to save a copy of your comments until your stakeholder team gives you access to their Slack #stakeholders channel. Let them know if you cannot access all of their materials by the end of lab 4.

3. Review your teammates with respect to the following aspects of their work on your team. The agreement value is on a standard Likert scale (1-strongly disagree; 2-disagree; 3-neutral; 4-agree; 5-strongly agree).

   Characteristics		Agreement	Comments
   Communication	Stays in contact with other team members.	1 - 2 - 3 - 4 - 5	Do they keep up with the project management tools? respond to email?
   	Stays on topic during meetings.	1 - 2 - 3 - 4 - 5
   	Deals with conflict openly and respectfully.	1 - 2 - 3 - 4 - 5
   Contribution	Finds and fills a useful role on your project.	1 - 2 - 3 - 4 - 5	If yes, which role (or roles)?
   	Does their share of the work.	X%	Estimate what percentage of the work this team member has done relative to the others.
   	Steps in to help others when needed.	1 - 2 - 3 - 4 - 5
   Engagement	Shows up on time (or make alternate arrangements).	1 - 2 - 3 - 4 - 5
   	Meets deadlines.	1 - 2 - 3 - 4 - 5
   	Is passionate!	1 - 2 - 3 - 4 - 5

   Include your assessment and comments in a copy of this: Team Member Review chart. Copy/edit this sheet as appropriate and then save/submit it as a XLSX (or CSV if needed) named memberReview.xlsx, and submit it in Moodle (so that it’s private!).

Checking in

Submit the files as specified above. We will grade your work according to the following criteria:

• 50% — Application (on GitHub)
• 30% — Team deliverable review (to Slack)
• 20% — Team member assessment (to Moodle)

Homeworks are always due by the due date for the following week’s lab (e.g., this one is due by the lab #4 due date/time).