connect-fertility-API

Running Server: npm run dev Running Client: npm run start

Core Functionalities that were achieved:

• User Authentication and Sign-up/Login - Utilizes NodeMailer to confirm user account email and encrypts user passwords
• User Profile - Allows users to upload profile pics and other photos they want associated with their account. Other relevant medical information is managed through PostgreSQL
• Chat and Swipe Functionality - Works similarly to dating up in which people are able to view profiles that fit the filters that are implemented and can like or dislike a profile.
• Chat Functionality: Maintained using Google Firebase and allows real-time chat features when clients connect

Bugs and possible glitches:

1. There is a bug when the user fills out info for their profile that causes an error, and the form isn't submitted. It is usually fixable: refresh. For some reason, the API calls to the Google Firestore database are sometimes randomly rejected and need to be refreshed.

2. The changed password doesn't work right now because of the addition of the Google Firebase Store database. I know how to change the password when it comes to PostgreSQL I struggled to figure out how to change it on the Google Firestore base and keep track of users.

3. The swiping functionality starts working after a user reaches Preferences and hits the change preferences once. This is because I didn't have enough time and I had to use localStorage instead of an external database to store the user filters. Because that is not the implementation method, user preferences are not saved, so they need to be changed each time a person logs in.

4. There could be a potential issue with how chats are added in the chat window. Currently, chats are made available between users when they match. The option to delete an account hasn't been added yet, so there wasn't a chance to debug and make it work smoothly so that chats are deleted when users no longer exist.

Changes need to be made to run on a different laptop:

1. Prominent changes need to be made, like creating a PostgreSQL account; there is code that creates all the necessary tables in the code.
2. For Cloudinary, the person has to create an account and fill out their API key for the Cloudinary account
3. Similar to Google Firestore, the person has to create their account and plug in the relevant information for their account
4. Nodemailer must also be configured for each person trying to run it. There needs to be an email provided and a key to permit the person to use the email to send verification emails

Demo Videos: https://www.youtube.com/@richarddzreke4131