A fitness tracking/logging application with social media aspects. The purpose of Resolute is to encourage users and their friends to be involved in each other's fitness endeavors through non-intrusive mobile notifications.
Overview:
The goal of this branch was to allow new users to register with the Resolute app. Changes were made to allow for user entry on the registration fragment, and many database queries take place to ensure the entered data does not conflict with already existing user data.
Description:
Adds UI textboxes to registration screen fragment, and has many tests to ensure user entry matches requirements for user data, and does not attempt to register under a username or email address that is already claimed by another user. Network features were also added that ensure that the user cannot attempt registration in any way while not able to connect to the Firestore database stored in our Firebase project's server. This was done to prevent the offline data-caching persistence functionality of Firestore from allowing users to register to Resolute without actively being connected to the internet. If there were possible, new users would be able to cache their registration locally, then push that cached user data to the server later on, even after another user may have already claimed their username or email, causing a clash, and allowing the new user to access the existing user's information. Many toast messages describe to the user their registration status at any given attempt to register.
Overview: The goal of this branch was to allow new users to register with the Resolute app. Changes were made to allow for user entry on the registration fragment, and many database queries take place to ensure the entered data does not conflict with already existing user data.
Description: Adds UI textboxes to registration screen fragment, and has many tests to ensure user entry matches requirements for user data, and does not attempt to register under a username or email address that is already claimed by another user. Network features were also added that ensure that the user cannot attempt registration in any way while not able to connect to the Firestore database stored in our Firebase project's server. This was done to prevent the offline data-caching persistence functionality of Firestore from allowing users to register to Resolute without actively being connected to the internet. If there were possible, new users would be able to cache their registration locally, then push that cached user data to the server later on, even after another user may have already claimed their username or email, causing a clash, and allowing the new user to access the existing user's information. Many toast messages describe to the user their registration status at any given attempt to register.
Removed/Changed tags: N/A
Closes #22