🚀 Feature: "Native" Sign In with Apple

[Lucke0051]

🔖 Feature description

Currently the Sign In with Apple implementation requires the user to firstly click accept on the prompt to "APPNAME wants to sign in with APP.com", then a blank browser window pops up and shortly after the Sign In prompt shows. This is not a nice user experience.

Instead the Sign In with Apple prompt should open right away when called (button pressed usually) on Apple devices that support it. See Flutter package sign_in_with_apple. This would provide a much nicer sign in flow. The "native" prompt also shows the app's icon and name without any configuration. I can implement this in the Flutter client SDK but I am not a backend PHP developer.

Current "flow":

"Native":

🎤 Pitch

As Apple requires developers to provide Sign In with Apple functionality if they have other third-party auth providers. This means that it's likely many people that will be positively affected by this change. 3 prompts to get to the sign in dialog is not ideal.

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

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[eldadfux]

Hey @Lucke0051, thanks for submitting this issue. We have been looking at this PR which wasn't completed as a potential solutions: #903. The idea behind it is to allow devs to use native OAuth SDKs for better UX.

We intentionally avoided coupling any of the Appwrite SDKs with 3rd party OAuth integrations. Today we have around 25 OAuth providers and 4 client SDKs. This can result in maintaining ~100 different integration, most of them probably not well maintained. This will also explosively increase the size of the SDKs and will force dependencies that will never be used in many cases.

We're still very open to continue the solution started at #903, if the community picks it up, we can also prioritize it.

[SirusCodes]

Is there any progress?

[KhaleelSH]

Any news here?

[zandercodes]

In one of the first versions of AppWrite it was possible to validate the login using Apple's indentityToken.
But this was removed in AppWrite. So the native login on the device is only possible via very complicated detours, which does not have to be.

[DorianMartinez]

Is this really ever going to be addressed? The user experience with the current implementation is subpar and far from what Apple users expect.

[cd711]

can I implement with functions self?

[zandercodes]

can I implement with functions self?

I don't know, try it

[stnguyen90]

I'm pretty sure native login should work now using custom tokens.

[SirusCodes]

I'm pretty sure native login should work now using custom tokens.

Thanks, this will surely work but it's again a bit of a hassle, as the dev will need to write code for verifying the tokens and implement a function just for this. I was kind of expectating a much easier way to do it like -

account.createGoogleAccountUsingToken which will do all that for me

[hapsai]

I'd just like to add a "me too" to this request. I'll try the custom token solution mentioned above - but being able to authenticate an apple user in an apple app without having to launch a web browser seems like a "must have" capability to me.