This semester, we've learned some great tools for frontend, backend, and database development. Now, we will put them all together to make an amazing final project!
This project will involve building a web app complete with a backend that connects to a Firestore database.
You will be working in groups of 2 to complete this final project. Your method of collaboration is up to you, but using GitHub is strongly advised. VS Code also has an excellent live coding tool which you can use if you prefer to do all work together.
- Firebase authentication system
- Create a backend using GET and POST requests
- Have a React frontend which talks to the backend and puts/fetches data from the database.
- Use conditional rendering (at least once)
- Use ES6 syntax (includes arrow functions, spreading, destructuring)
- Use Functional programming (map/filter/reduce)
- Use React Hooks
- Use TypeScript (and code is well typed, so no
- Picnic items
- Card game
- Chat bot
- Songs browsing website
- Social network
- School management DB
You are not limited to these ideas, they are just some things we've seen in the past that might help you get started!
The project will be divided into a number of milestones to help you progress in a reasonable way.
Each milestone is due before lecture on its due date. Your remaining slip days are still valid for this. If you and your partner have different number of slip days left, the partner with the most slip days left counts. e.g. if Peter and Becky are a group and Peter has 5 slip days and Becky has 3, we are allowed 5 slip days for the final project. You are allowed to use at most 3 slip days per each of Milestones 1, 2, 3.
Due: April 11 by 11:59 PM (no slip days)
Please fill out this team matching form by Sunday, Apr. 11th. This is a hard deadline because we want to assign partners on Sunday so you have enough time to work on Milestone 0 (due by next class).
Due: April 15 by 3:59 PM (no slip days)
Upload to CMS a mock and description of your web app! Your mock can be a picture/pictures (handdrawn or created from a drawing program) and the description should be in
Due: April 29 by 3:59 PM
Get started implementing either the frontend or backend (you choose). If you're doing frontend, you can use hardcoded data for now just to get the layout done. This can be default values embedded in your frontend code like we had for Thinking in React lecture 7. You will connect it to a backend in the subsequent milestones.
Due: May 6 by 3:59PM
Work on the other side (if you did frontend for Milestone 1, do backend now and vice versa).
Also have an authentication system set up using Firebase.
Due: May 13 by 3:59PM
Bridge the frontend and backend together using data fetching. This will involve some full stack work! Also, the app should be fully deployed on Firebase and styled using any CSS you deem necessary. This is your final submission!
Need help? Come to office hours and we can help you debug. Also feel free to post questions on Piazza!
Do not push private API keys, Firebase service accounts, or other sensitive information to GitHub. Similarly, do not push
node_modules up to GitHub/Heroku. If we see these in your GitHub, you will lose points.
Do, however, submit your keys in your CMS submissions if they are necessary to run your app. Don't worry, your secrets are safe with us :)
If you're looking for an added challenge, consider doing one or more of these extensions! There is no extra credit for these extensions, but it will really enrich your understanding of webdev (and make us very impressed!) :)
- Use Material-UI or Bootstrap (libraries to help with styling!)
- Use an external API with your backend (note: this doesn't replace your Firebase backend)
- Use of ES6 & TypeScript
- Component structure
- Use of hooks
- Functional programming
- Use of ES6 & TypeScript
- Has both GET and POST requests
- Is connected to a database
- Functional programming
- Data fetching
- Data insertion
- Authentication (using Firebase auth)
Code style and file structure (5%)
- This may seem like an arbitrary measure, but we expect most people to get most of the points here; the only way to lose points is if it is clear that not a lot of effort has been put in or you are consistently missing milestones.
Submission for each milestone will be a zip file of your code, along with a README containing a description of the project, a list of group members and netIDs, a link to the deployed site, a link to the GitHub repo if you used GitHub, and anything else that you think is important for us to know.
As always, do not include your
- Get in contact with your partner early!
- Milestone 0 is intended for you to get some discussion on what you want to build before you start implementation. Make sure you are both aligned on what needs to be built to avoid issues later on. Better initial planning means less frustrations later on.
- Be realistic.
- We know you are ambitious but also understand your own capabilities. Building something too complex may be too overwhelming. You are allowed to change ideas, but that would be time wasted on the old project.
- Use GitHub
- GitHub is the best tool for sharing code between you and your partner/team members. Please use GitHub instead of emailing code back and forth to each other.
- Use branches!
- When developing a feature, you should open up a new GitHub branch rather than committing and pushing directly to master. This will allow you to develop your feature independently of the current state of master (and what your partner is doing) and only merge in when you are sure your feature is done and works.
- Branches can also protect you from weird frustrating merge conflicts (so you can focus on developing awesome features!)
- Pair programming is fun!
- Ideally, you should both be actively involved in the whole development process. A good way to achieve this is to step up a time to pair program and code together!
- Also refer to tips in How to Lose in CS 2112