Skip to main content
Version: 2022sp

Final Project

This semester, we've learned some great tools for web development. Now, we will put them all together to make an amazing final project!


This project will involve building a React web app complete with a connection to a Firestore database.

You will be working in groups of 3 or 4 to complete this final project. Your method of collaboration is up to you, but using GitHub is strongly advised.


  • Firebase authentication system
  • Firestore database connection on Frontend
    • Create, Read, Update, Delete operations
  • 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 any)
  • Use Next.js with at least 2 pages

Suggested Project Ideas

  • Picnic items
  • Clicker game (more involved)
  • Blog
  • Forum
  • Wiki
  • 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.

Your remaining slip days are still valid for this. The group's allotted slip days is the max of your group members'. You are allowed to use at most 3 slip days per each of Milestones 1, 2, 3.

Team Matching Form

Due: April 17 by 11:59 PM (no slip days)

Please fill out this team matching form by Sunday, April 17th. This is a hard deadline because we want to assign group members on Sunday so you have enough time to work on Milestone 0.

Milestone 0

Due: April 22 by 11:59 PM

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 pdf form. Your mock should include sketches of the different pages or views in your application. Your description should be at least 200 words and elaborate on what your project will be about. Also consider how you will structure your database schema! (What collections will you need, how will they be related, and what documents will they store). Finally, if you are using GitHub (highly recommended!), please link it in your description (and make the GitHub repo public). Please zip both of these together to submit to CMS.

Milestone 1

Due: April 29 by 11:59 PM

Get started implementing the frontend. Use hardcoded data for now just to get the layout done. This can be default values embedded in your frontend code. You will connect it to the database in the subsequent milestones.

Milestone 2

Due: May 6 by 11:59 PM

Connect the app to Firebase by replacing hardcoded data with database calls.

Also work on having an authentication system set up using Firebase Auth.

Milestone 3

Due: May 13 by 11:59 PM

This is the last milestone!

Finish up the authentication system on your site and deploy your website.

Include the url of your deployed site in your submission!


Need help? Come to office hours and we can help you debug. Also feel free to post questions on Ed!


Do not push private API keys, Firebase service accounts, or other sensitive information to GitHub. Similarly, do not push node_modules up to GitHub. If we see these in your GitHub, you will lose points.

Note that firebase configs for the frontend are fine (and should be) included in your submission

Optional Extensions

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!) :)

  1. Use Material-UI (MUI) or Bootstrap or Semantic UI or Chakra UI (component libraries that help with styling!)
  2. Make your website mobile-friendly/responsive
  3. Use an external API (in additional to your Firebase backend!)


  • Frontend (35%)

    • Use of ES6 & TypeScript
    • Component structure
    • Use of hooks
    • Functional programming
  • Database/Backend (15%)

    • Data fetching
    • Data insertion
    • Data deletion
  • Auth (10%)

    • Authentication (using Firebase auth)
  • Styling (5%)

  • Deployment (5%)

  • Code style and file structure (5%)

  • Effort (25%)

    • 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 node_modules.

Tips for Success!

  • 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 git
    • git is one of the best (and prevalent) version control systems out there. It is great for sharing code between you and your partner/team members. Please use a service like 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 the main branch. This will allow you to develop your feature independently of the current state of main (and what your partners are 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