To ensure that the website functions properly as the application grows in complexity, integration and end-to-end (E2E) testing will be necessary.

Learn more about E2E testing here.

Learn more about integration testing

Some parts in the codebase tend to use "any" types (see this search query for "any". Unless there is a solid reason for using "any", I want to replace these types with explicitly defined types. Eliminating these types would make code more readable and therefore easier to debug.

Rather than the user uploading one picture at a time, allow the user to upload multiple pictures at once (up to a defined limit).

The current email logins don't verify if the email is valid or not. In order to prevent invalid, unverified emails from taking up storage space in Firebase Auth, use Firebase Auth's passwordless sign-in using email links. This would also remove the need for passwords, ensuring better user security.

Reference: Firebase Auth Docs

I want to create a function that will purge a user's history. This will allow the user to look at the pictures they clicked on in the past once again. This will mainly be for development purposes, though. This could be used for production, but I really do not see any reason why.

Description

While running test cases (see #10), I've noticed that the API endpoint, /api/images, tends to throw 500-related errors (see below). There are multiple causes for this, where one is the logic for fetching images. The other is making too many calls to Google's API.

Solution

I propose we use Redis to alleviate our API and Google's API. This would not only speed up our application but prevent repeated calls to Google's API and thus save on potential costs.

The website design (as of now) seems very bare-boned. The tool we went with to accomplish the job is TailwindCSS. We plan to stick with it as it speeds up development time. Let's beautify it and make it look pretty for the public ☺️

EDIT: Some of the early comments made by me are mainly for progress checks.

Implement social logins (i.e signing in with Google, GitHub, etc.) through Firebase Auth for users to use for account creation and login.

This can be done in conjunction with #6 to improve the overall user authentication experience.

The README needs to be updated to discuss the project, its software architecture, and the main overview of its primary features.

As the saying goes: "a picture is worth a thousand words."

By adding screenshots of the website in the README and in the "Social Preview" section of the project's settings, we will be able to show future users and developers the general visuals of the project.

Rather than creating a separate Firebase project for local development, we can use Firebase's local emulators to test our logic on Firebase services. So far, there are local emulators for Authentication, Firestore, and Storage.

References:

1. Firebase Local Emulator Docs

Add a button that toggles light/dark mode for the user.