[MW-225] feat(auth): Implement full Sign In & Sign Up flow with validation

[HekmatullahAmin]

Jira Task: MW-225

Screenshots

SignIn.SignUp.mp4

Description

What’s Achieved in This PR

1. Implemented full Sign In and Sign Up flow

• Covers both happy and unhappy user journeys.

• Seamlessly transitions from input to account creation and navigation.

2. Added robust user input validations

• Ensures mandatory fields like name, email, and mobile number are filled.

• Email is checked for correct format.

• Password and confirm password must match.

3. Improved error handling

• All validation and API errors are now clearly presented to the user.

• Replaced generic or null messages with user-friendly alternatives.

• Handles unique field validation (username and mobile) with clear feedback.

4. Password requirement hinting

• A help card shows password rules inline before submission.

• Prevents trial-and-error by guiding users upfront.

5. Updated pin code validation

• Removed strict 6-digit requirement for pin codes.

• Allows shorter lengths to support different country formats (e.g., 4- or 5-digit codes).

6. Country and state dropdown integration

• Integrated stefanbinder/countries-states JSON for populating country-state mapping.

• Countries and their respective states are loaded from countries.json and rendered as dropdowns in the signup form.

• Apply the AndroidStyle.xml style template to your code in Android Studio.

• Run the unit tests with ./gradlew check to make sure you didn't break anything

• If you have multiple commits please combine them into one commit by squashing them.

[HekmatullahAmin]

@niyajali could you please have a look here

[niyajali]

@HekmatullahAmin Fetch Country & State from server and show as drop-down if any API available otherwise create a list of country and state and show as drop-down.

And instead of dialog for password feedback show a card below of the password indicator which should contain list of password feedback.

[niyajali]

And update the PR title like [MW-225] - The PR Title

[HekmatullahAmin]

@niyajali can you have a look at here i created the interface if the want the data from json then they can create a function accordingly

[HekmatullahAmin]

@niyajali just wanted to clarify the UX expectations here:

Would you prefer:

• Show red outline + support text even when the field hasn't been focused yet (i.e. as soon as the screen loads),
• Show only a *required message below each field (no red border or red support text styling),
• Or some other validation behavior?

[niyajali]

@HekmatullahAmin What type of validation we had earlier

[HekmatullahAmin]

@HekmatullahAmin What type of validation we had earlier

@niyajali previously it was only dialog if someone click submit it was showing the field must not be empty

[niyajali]

@HekmatullahAmin Okay so currently you're passing some errorMessage on the text field initially, and what is that message

[HekmatullahAmin]

@HekmatullahAmin Okay so currently you're passing some errorMessage on the text field initially, and what is that message

yes the message are all like this field cannot be empty.
for example username is required
address line 1 connot be empty
...

and will only show if they are empty and is focusable, so if the go to another field it shouldn't show. if not focusable and the user visit the sign up screen for the first time all of those fields is going to look red with their error message.

do you want me to keep it or revert it back to before or u want sth else?

[niyajali]

Those error messages we're showing on the dialog right, so do not need it, revert to the original

[HekmatullahAmin]

@niyajali I revert it and also removed the isError from composables in SignUp Screen. Previously it was passed from the SignUp screen checking if those were empty but in MifosTextField the isError was not passed.

• So as previously there were no red error container nor error message i removed them

[HekmatullahAmin]

@niyajali i revert those changes just one thing more how you want the behavious of PasswordStrenghtIndicator:

• to be shown always when the user navigate to SignUpScreen?
• or to be shown only if it is clicked in the password field and hide when user navigate to another field?

@biplab1 thanks for pointing i will fix the typos

[niyajali]

As we've created the indicator card those are only visible when the focus state has been changed.

[HekmatullahAmin]

@niyajali added the neccessary changes if looks good approve and merge

[HekmatullahAmin]

@biplab1 could u please resolve your requested changes and approve

[HekmatullahAmin]

@itsPronay , @revanthkumarJ , @biplab1 when u are available have a look and resolve your conversation and kindly approve