CS 347: Project 2 – React App – due December 13
In the second project of this course, you will create a web app that consumes a web service. The subject of the app is not specified; you pick its purpose. You will use several tools from the Node.js ecosystem, including React, Redux, and Express.
Your app must meet the following expectations:
- You will create an app that has a coherent purpose and satisfies a personal creative itch.
- You will not write a to-do list management app.
- You may work with a partner or as an individual.
- The code must be written by you and your partner, and any assets must be made by you and your partner or conform to their license.
- Your app will have both a back-end data store and web service and a front-end client.
- You will create a front-end client using React’s functional components and hooks. (Do not use classes for making components.)
- The content of your client must change dynamically as the user interacts with it. (Sites with only static content generally should not be written with React.)
- You will manage state in your client using Redux.
- The user interface of your client should follow the aesthetic and usability principles described in project 1, including clean spacing, coherent alignment, sufficient contrast, harmonious colors, and responsive design.
- You will access your web service from your client using your own calls to
fetch and not through any helper library.
- You will indicate asynchronous activity to the user via the GUI. For example, while a fetch executes, you show a progress wheel.
- Your client must be free from all warnings and errors.
- Your front-end client must be stored in a Git repository that you have shared with your instructor. On GitHub, GitLab, and Bitbucket, share with the user
- Your front-end client must be available through the URL
https://project2.YOUR-DOMAIN-NAME. It must be served out via HTTPS over port 443. If visitors access your client through port 80, they must be redirected automatically to port 443. The configuration is very similar to that of project 1.
- Your app will store its data long-term in a relational database. There’s nothing wrong with NoSQL databases like MongoDB, but they are intentionally outlawed to align our focus and to give us more experience with relational databases. Your database need not have multiple tables.
- You will provide an Express-based web service for interacting with the database. The service must only be directly accessible from your droplet, and not from outside. Use
ufw to block all ports but the ones you need for SSH and your allowed web servers.
- The web service must communicate send and receive complex data as JSON.
- The endpoints of the web service and any parameters should be appropriately named.
- The web service must support cross-origin resource sharing.
- Your web service must be started using a process manager like
pm2 so that it stays running.
- You will create an Nginx server that allows global, encrypted access to your web service.
- Your back-end must be stored in a separate Git repository that you have shared with your instructor. On GitHub, GitLab, and Bitbucket, share with the user
By the due date, share in the top-level directory of your front-end client a file named
README.md. In this file, write a brief but itemized breakdown of how you believe you have met the expectations listed above.