FR: Allow modification of passwordless sign-in email template

[exo-pla-net]

Operating System

n/a

Browser Version

n/a

Firebase SDK Version

n/a

Firebase SDK Product:

Auth

Describe your project's tooling

n/a

Describe the problem

The default passwordless sign-in email is unprofessional and confusing to users.

For developers, it makes using Firebase under the hood of our apps embarrassing.

For instance, in the sign-in email:

• Instead of specifying the name of our company or our app, the email instead suggests to users to users that they can sign in to our firebase project id. This is typically an ugly string we selected owing to its availability. Even if the user manages to make the connection between the ugly string and the app they just signed up for, they are certainly not going to be impressed that we were apparently too lazy to make our emails reflect the name of the thing we're actually selling.
• The email closes with "Thanks, your ugly-project-string team". In the majority of cases, THERE IS NO TEAM, and if there is a development team actively overseeing the app, it certainly isn't the ugly-project-string team (leading to internal confusion), and even if there is such a team, the end user need not and ought not know about it. We're closing with an unprofessional lie/fabrication that helps make these sign-in emails have an uncomfortable overlap in form and factor with a scam email from Nigeria.

I get that there is a security concern with allowing complete freedom with these emails, but I am sure there are better ways to improve security than by forcing all Firebase developers to embarrass themselves with their sign-in emails.

Steps and code to reproduce issue

N/A

[jbalidiong]

Hi @exo-pla-net, thanks for reaching out to us. This seems to be a backend issue and not an SDK issue. I would suggest fling this feature request to our Firebase support channel. I'll be closing this issue now. If you encounter another issue, feel free to create a new one.

[exo-pla-net]

I will not be doing that, as that would be sweeping this issue under the rug. It's darkly humorous that the fact passwordless sign in exists was due to a FR here, but fixing it is beyond scope.

As any developer would expect to be able to modify the email template, I am certain that I am not the only developer who was bait-and-switched into wasting precious development time on a half-baked feature.

The fact that there is no public forum for issues that don't fit neatly into certain boxes is another cause for concern re: Firebase. The word on the street is that Firebase is for prototypes; when you want to do something serious, you move to Amazon.

How Firebase apparently treats issues for developers interested in using Firebase for enterprise lends ammo to this narrative. The issue was closed, and the buck wasn't even passed along.

Thanks, your ignored-issue-4236 team