avoiding conflict of link for OAuth for apps with the same proejct

[Silfalion]

🚀 Feature

This feature would consist in a change in the flutter(and Android?) sdk code, at least since I don't know if this would be relevant for the other SDK to change the app scheme to something unique for each app.

Have you spent some time to check if this issue has been raised before?

yes

Have you read the Code of Conduct?

yes

Pitch

This comes from the following problem: if an ecommerce platform is made with both a customer and shop apps and they both use the same appwrite project, the scheme to open the OAuth2 window for identification would look something like appwrite-callback-[PROJECT-ID]. Now if you try to OAuth2 with the customer app with a say google account this will give you a choice of which Flutter_web_auth instance(?) you want to use, the customer or shop app. Providing that you tap on always and select your choice, the next time you're in the shop app and OAuth the callback will take you to the customer app and not the shop app you identified from.

A potential solution for this would be to let the user add a keyword to the callback scheme such as appwrite-callback-[PROJECT-ID]-[KEYWORD] or simply to allow the user to choose a scheme of their own. In both cases this would require to add a new parameter to the client class where the user would specify said keyword/scheme.

[Maatteogekko]

I also stumbled upon this issue while testing two different versions of the same app. So I would like to have a solution for this

[Silfalion]

Idk for other platforms but for Flutter we could add a function when setting up the client as in: .setCallbackKeyword("keyword")

Then save it in the config map and add it later on.