Integrate code from your solutions to labs 4–6 to display the names and details for the product items from lab 6 (e.g., see the image to the right). Include the following features:
- Lab 4 — Use a tabbed UI design that includes
an about page (e.g., the sample image shows two tabs: items
and about). As in the lab, use a file-based layout directory
(q.v.,
(tabs)/). - Lab 5 — Include an index page that lists a
sub-set of the product item details, and a separate details
page that lists all the details (e.g., there are three
products listed on the product items page, and the full
description of one product on the details page). As in the
lab, include the data into context (q.v.,
ItemContext.ts). - Lab 6 — Pull the product data from the static
JSON file used in the lab (q.v.,
await fetch()).
As with the previous homework, use Copilot to help you build this app. But don’t let Copilot give you just anything. Follow the best practices from the labs.
Do all of this in a homework2/items-app/
sub-directory. When you have the app running on your device,
delete a couple of the items, save a screen shot of your
item index screen (homework2/screenshot.png), and
add a new readme file (homework2/README.md) that
answers the following questions:
- We’ve used ReactNative context to store app state. Name one other alternative and explain whether it would be better to stay with context or to switch.
- When does the app actually load the item data? What ReactNative hook is used for this?
- How effectively did Copilot work for you on this assignment? Include examples of things that it did correctly and/or incorrectly.
Submit this application by pushing it to your cs262
repo (under homework2/).
Review the sprint 2 deliverables from your stakeholder team (see project deliverable #2) and comment on the following:
- Are their class and UI models well-formulated? Do they describe a coherent system? Do they include non-functional requirements?
- Has there been an appropriate amount of code pushed into their client repo? Can you run the prototype? If so, does the application make sense to you?
Post your review to their Slack #stakeholders
channel
and be prepared to explain your review to them during their team
meeting in lab 7.
Review your teammates with respect to the same aspects of their
work on your team as you did last time. Focus, in particular, on
changes. Is anything getting better or worse? Include this in a
separate tab named homework2 added to the
spreadsheet you submitted for homework 1. Be sure to download
“All sheets”.