Threads
Loading user profile...
+1 for this this change has real impact on mobile developers. I've built full-stack apps using Supabase Auth and the link based flow is genuinely painful on mobile. Deep linking is fragile it breaks differently across Android and iOS versions, email clients, and when users have browsers that intercept links. A 6-digit OTP that users just type in is a far smoother experience. The request here is very reasonable not asking for free text template editing, just a toggle or a second locked template variant that uses {{ .Token }}. That's a minimal change with a big UX improvement for mobile developers. The custom SMTP + verified domain requirement is a significant barrier, especially for students and indie developers just getting started. Many of them choose Supabase specifically because it lowers the barrier to building this change raises it again for a common use case. Hope this makes it onto the roadmap soon.
+1 for this feature request! As someone who has built and deployed full stack apps using Supabase as the backend (PDF Ghar - pdfghar.in and Cresolve - cresolve.in), I've felt this pain firsthand. Currently I use AWS Amplify and Vercel for frontend hosting alongside Supabase, which means managing separate dashboards, billing, and deployment pipelines. Having frontend hosting natively on Supabase Cloud would make it a true full stack platform especially useful for indie developers and small teams who want a single place to manage everything. The unified billing alone would be a big win. This would also pair really well with Edge Functions and the existing auth/storage/database setup. Would love to see this on the roadmap!