Currently, phone authentication supports providers like Twilio, MessageBird, Textlocal, and Vonage. While these are solid options, they can be limiting due to pricing, regional coverage, and country-specific support.
To improve flexibility, allow users to define *custom phone authentication providers. for example via Edge Functions or a similar mechanism. Users could implement standardized functions such as send_otp and verify_otp that behave like the built-in providers.
This approach would:
Dev-Salem suggests allowing users to define custom phone authentication providers to improve flexibility and reduce dependency on existing vendors. This would enable integration with any SMS provider offering a REST API, enhancing global coverage and cost optimization.