Replies: 1 comment
-
|
Strong +1 on this. Email-link flows are fine on web, but for native/mobile apps they add a lot of friction because deep-link schemes like myapp:// are often blocked or stripped by email providers. Requiring universal links/app links plus hosted redirect infrastructure just for reset/verify is heavy for small teams. Supporting email OTP for password reset and email verification would make native flows much simpler and more reliable: If implemented, it would be great to keep both options (link + OTP) configurable per project so teams can choose based on platform and security requirements. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🔖 Enhancement description
Currently appwrite uses link system which send a link to users which they use to redirect to the application. This works fine for web apps but for native apps, we cannot send
myapp://like scheme to get redirected to our apps. Because mailing service dont allow any other protocols except https. The native app scheme looks like a protocol and mailing service blocks theNot an httpslike scheme. It just strips the url away from the mail itself. Even if the url/scheme is sent in some hacky way the mail providers still block it by not allowing the users to click on it.🎤 Pitch
We either have to host a site and implement universal linking/ app linking or use a cloud function that redirects back (too much complecated). And not everyone wants to host a site for every app they make. The simple solution would be to use the Email OTP method present in appwrite to be used for password reset and email verification also.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
Beta Was this translation helpful? Give feedback.
All reactions