Hey Product Hunt! 👋
I’m excited to share something I’ve been working on: an authentication service specifically built to make Firebase Authentication even more convenient for web and mobile developers. 🚀
As someone who’s built a lot of apps for clients, I’ve always loved Firebase for its simplicity and generous free tier. But every time I had to implement authentication, I found myself redoing the same work like styling the UI, adding custom fields, tweaking password strength, or fixing things for edge environments like Vercel or configuring CAPTCHA. I also wanted features like user invitations that are not provided by Firebase.
I built this service to make things easier, for myself and for others. Here are some of the features:
- Fully customizable authentication UI (no more default modals!)
- Support for custom email templates and password policies
- Seamless integration with Next.js and edge platforms like Vercel
- Features like bot detection, user invitations, and custom fields during registration
- More, check Firefuse homepage
The goal for me is simple: save you time and make Firebase authentication a better experience for all devs.
If you’ve ever been frustrated with Firebase’s default auth or had to build something custom, I’d love to hear your thoughts. Does this sound like something you’d find useful?
If it is something that you would be interested in, let me know, this will give me more fuel to finish the MVP and publish it.
If you would like to be one of the first users, please subscribe on our homepage and I guarantee that there will be amazing bonuses.
Thanks for checking it out!
@ziolmar, congrats on launching Firefuse!
Bot detection solves a lot of common pain points.
One thing we have struggled with is disposable emails & aliases using +. Any plans to prevent those emails?
@ashitvora Great suggestion, I was also working on the project where this was required. I see here some additional use cases for example limiting access to only specific domains, as this would be relatively simple to implement for an email/password, for cases where you use for example google auth you have to do this after the authentication is done. I will add it to the backlog.