Notes

Onboarding | Login "As a user, I want to enter my email and passcode to log in to the app.

Acceptance Criteria:
The login screen should have separate fields for entering the email and passcode.
The email field should accept valid email addresses.
The passcode field should mask the entered characters for security.
The login button should be disabled until both the email and passcode fields are filled.
Upon successful login, the user should be redirected to the app's home screen.
If the email or passcode is incorrect, an error message should be displayed, indicating the reason for the login failure.
The app should handle any server-side errors and display appropriate error messages to the user.
The app should have a ""Forgot Password"" option to help users recover their account in case of a forgotten passcode.
The password must consist of exactly 8 characters.
The password can include a combination of uppercase letters (A-Z), lowercase letters (a-z), numbers (0-9), and special characters (e.g., !, @, #, $, %, ^, &, *, etc.).
At least one character from three of the following categories must be included in the password:
a. Uppercase letters (A-Z)
b. Lowercase letters (a-z)
c. Numbers (0-9)
d. Special characters (e.g., !, @, #, $, %, ^, &, *, etc.).
The password must not contain any spaces or tabs.
The password should not be easily guessable or commonly used, such as ""password"" or ""12345678"".
The password must be unique and not match any previously used passwords by the user.
The password field must provide clear and concise instructions or error messages to guide the user in meeting the specified requirements.
The password entry field should be masked to hide the characters being typed to ensure privacy and security.
The password policy requirements should be communicated to the user during the password creation process.
The password policy should be enforced and validated on both client-side and server-side to ensure consistency and security."
Social Media Login and Signup "As a user, I want to be able to log in and sign up using my Google or Apple accounts.

Acceptance Criteria:
The app should provide options to log in or sign up using Google and Apple accounts.
Tapping on the Google login/signup option should initiate the Google authentication process.
Tapping on the Apple login/signup option should initiate the Apple authentication process.
After successful authentication with Google or Apple, the app should create a new user account if it doesn't exist or log in to the existing account.
The user should be redirected to the app's home screen after successful login or signup.
The app should handle any authentication errors and display appropriate error messages to the user."
Signup - Junior "As a Junior user, I want to sign up by providing my
Name,
Email,
Mobile number,
Country of residence,
Profile picture(optional),
Gender,
Date of birth
Guardian Code (optional), and
Referral Code (optional).

Acceptance Criteria:
The signup screen should have fields for entering the required information: Name, Email, Mobile number, Country of residence, and Profile picture.
The signup screen should have an optional field for entering the Guardian Code.
The signup screen should have an optional field for entering the Referral Code.
The app should validate the entered email to ensure it is in the correct format.
The app should validate the entered mobile number to ensure it is in a valid format.
The app should display appropriate error messages if any required fields are left blank or if any entered information is invalid.
Upon successful signup, the user should receive a verification email with a passcode to verify their email address.
After verifying the email, the user should be redirected to the app's home screen.
The app should provide a signup form with input fields for name, email, mobile number, country of residence, profile picture, Guardian Code (optional), and Referral Code (optional).
If a Junior is directly invited by a Guardian, the signup should be approved by the Guardian.
If a Junior signs up independently, they should enter the Guardian's information(optional).
A Junior signing up with a Guardian's invitation should provide the Guardian Code for validation.
The user must provide a valid Guardian code during the registration process, if applicable. The Guardian code should be validated against a predefined set of codes.
The user may optionally provide a referral code during the registration process. The referral code should be validated against a predefined set of codes.
The Guardian and referral code fields should provide clear instructions and error messages to guide the user in providing the correct code format.
The Guardian and referral code fields should not accept invalid or expired codes.
The user should receive appropriate feedback upon successful submission of the Guardian and referral codes."
Signup - Guardian "As a Guardian user, I want to sign up by providing my
Name,
Family name,
Email,
Mobile number,
Country of residence,
Gender,
Date of birth,
Profile picture(optional), and
Referral Code (optional).

Acceptance Criteria:
The signup screen should have fields for entering the required information: Name, Family name, Email, Mobile number, Country of residence, Gender, Date of birth, and Profile picture.
The signup screen should have an optional field for entering the Referral Code and Profile picture.
The app should validate the entered email to ensure it is in the correct format.
The app should validate the entered mobile number to ensure it is in a valid format.
The app should display appropriate error messages if any required fields are left blank or if any entered information is invalid.
Upon successful signup, the user should receive a verification email with a passcode to verify their email address.
After verifying the email, the user should be redirected to the app's home screen.
The app should provide a signup form with input fields for name, family name, email, mobile number, country of residence, gender, date of birth, profile picture(optional), and Referral Code (optional).
The maximum allowed size for profile picture uploads shall be 5MB.
When a user attempts to upload a profile picture, the system should validate the size of the uploaded file.
If the uploaded file exceeds the maximum allowed size of 5MB, an appropriate error message should be displayed, informing the user that the file size exceeds the limit.
The error message should provide clear instructions on how to reduce the file size and suggest alternative methods or tools to resize or compress the image.
The file size validation should occur on both the client-side and server-side to ensure consistency and prevent bypassing of the size limit.
The system should prevent the upload of oversized profile pictures, even if it is attempted through malicious means or unauthorized access.
If the uploaded file is within the allowed size limit, the system should proceed with processing and storing the profile picture.
The user should receive a confirmation message or indication of successful profile picture upload after the file has been processed and saved.
The profile picture should be displayed and accessible within the user's profile with appropriate dimensions and resolution to maintain a visually pleasing and professional appearance.
The profile picture upload feature should be tested with various file sizes, including files larger than the allowed limit, to ensure the error handling and validation process functions as expected.
The maximum size limit for profile picture uploads should be clearly communicated to the user in the relevant user interface or accompanying documentation."
Forgot Passcode - Reset Passcode "As a user, I want to be able to reset my passcode by receiving a verification code via email.

Acceptance Criteria:
The app should provide a ""Forgot Passcode"" option on the login screen.
Upon selecting this option and entering the registered email, a verification code should be sent to the user's email.
After verifying the code, the user should be able to reset their passcode.
The app should provide a ""Forgot Password"" option on the login screen.
When the user selects the ""Forgot Password"" option, they should be prompted to enter their email address.
The app should validate the entered email address to ensure it is in the correct format.
After entering the email address, the user should receive an email containing a verification code.
The app should display a screen where the user can enter the received verification code.
The app should validate the entered verification code to ensure it matches the one sent via email.
If the verification code is valid, the user should be directed to a screen where they can reset their passcode.
The passcode reset screen should have fields for entering a new passcode and confirming it.
The app should enforce any password complexity requirements (e.g., minimum length, special characters) during passcode reset.
After successfully resetting the passcode, the user should be redirected to the login screen.
Passcode expiration duration of 30 to 90 days"

CMS Pages "As a user, I want to access static CMS pages such as Legal, About Us, and Privacy Policy.

Acceptance Criteria:
The app should provide sections for accessing static CMS pages like Legal, About Us, and Privacy Policy.
Users should be able to navigate to these pages and view their content.
The app should provide a navigation menu or a dedicated section where the user can access static CMS (Content Management System) pages.
The static CMS pages should include commonly required pages such as Legal, About Us, and Privacy Policy.
The app should load and display the content of each CMS page when selected by the user.
The content of the CMS pages should be formatted appropriately for easy reading and navigation.
The app should provide a way for the user to navigate back to the previous screen or close the CMS page and return to the app's main interface.
The content of the CMS pages should be regularly updated as necessary to ensure accuracy and compliance with legal requirements.
The app should handle any errors in loading the CMS pages and display an appropriate error message to the user."