Integrating ZITADEL in a mobile app, UX issue
Hi, I’m integrating ZITADEL in a mobile app. I’d like users to log in natively with Google/Apple. Currently, when the user taps “Login with Google,” the app opens the browser where they see the ZITADEL login screen again (with Google/Apple buttons), so it feels like a duplicate step. Does ZITADEL fully support a flow where I can skip the extra login screen by exchanging the native Google/Apple ID token directly for ZITADEL tokens (token exchange)? And if yes, is there a recommended setup or example for mobile apps?
1 Reply
Hi @destbro7, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. Impersonation and delegation using Token Exchange ](https://zitadel.com/docs/guides/integrate/token-exchange) ) :
Token Exchange is currently a beta feature that allows exchanging tokens to different scope, audience or subject, but requires enabling it first and may not directly support the native mobile flow you're describing.
2. Native Mobile Android / IOS Google Signin ](https://discord.com/channels/927474939156643850/1213213568741281822) ) :
A community discussion about this exact use case where someone wanted to use Android/iOS native Google signin and forward the access token to ZITADEL, but the response indicated this wasn't directly supported at the time.
To learn more, see the sources I considered:
[1] Impersonation and delegation using Token Exchange
[2] Native Mobile Android / IOS Google Signin
Feel free to tag @Ask Inkeep with additional questions.