Implemented Supabase Google OAuth Authentication for Patient and Therapist Apps with Multi-Platform Support like Web, IOS, Android

[SharkyBytes]

Closes #17

📝 Description

This pull request integrates Supabase Google OAuth authentication for the patient and therapist applications, supporting iOS, Android, and web platforms. Key changes include:

->Added Google Sign-In functionality using Supabase in both patient and therapist apps
->Implemented platform-specific authentication flows for iOS, Android, and web
->Corrected folder structure for proper package version fetching in Android setup
->Added success and error snackbars for sign-in feedback
->Implemented user metadata retrieval for personalized welcome messages
->Set up appropriate post-authentication routing for each app
->Centralized Google Sign-In logic in widgets/google_signin_button.dart for both apps
-> Removed the unnecessary assets from the assets folder
-> Added the .env.example in both the apps so it would be easier to setup

To use:
-->Set required credentials in the .env file in both the patient and therapist apps
-->Test Google Sign-In across all supported platforms

📷 Screenshots or Visual Changes (if applicable)

Patient App

Recording.2025-03-19.141837.mp4

Made similar changes to therapist app too

Authentical Table in Supabase

✅ Checklist

• I have read the contributing guidelines.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if applicable).
• Any dependent changes have been merged and published in downstream modules.

[SharkyBytes]

Hey @mdmohsin7! I’ve implemented everything to the best of my knowledge. Could you please review it and let me know if anything is missing?

[mdmohsin7]

Move the logic to providers for both the apps please

[SharkyBytes]

Hey @mdmohsin7! Did the requested changes. PTAL

[mdmohsin7]

Pls do not use BuildContext in providers. The state and the logic should not depend on each other. And it is a good practice to keep the separation

[SharkyBytes]

Pls do not use BuildContext in providers. The state and the logic should not depend on each other. And it is a good practice to keep the separation

Yeah, @mdmohsin7, that makes sense! I've now separated the logic and handled UI navigation in a separate file. PTAL

[mdmohsin7]

@khanjasir90 since auth is a requirement for your assigned issue, can you pls test it once to confirm if everything works for you as well? Once done pls lmk and I'll review the code and will merge the PR

[khanjasir90]

@khanjasir90 since auth is a requirement for your assigned issue, can you pls test it once to confirm if everything works for you as well? Once done pls lmk and I'll review the code and will merge the PR

Sure

[khanjasir90]

@mdmohsin7 auth works fine in ios.
just a thing that REVERSED_CLIENT_ID has been hardcoded in info.plist file. this needs to be removed.

[mdmohsin7]

@SharkyBytes pls resolve the conflicts

[SharkyBytes]

Hey @mdmohsin7 Can you please check it now?