Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename the extension with Authenticator CC #718

Closed
Sneezry opened this issue Jul 22, 2021 · 2 comments
Closed

Rename the extension with Authenticator CC #718

Sneezry opened this issue Jul 22, 2021 · 2 comments

Comments

@Sneezry
Copy link
Member

Sneezry commented Jul 22, 2021

The simple extension name is a history issue. I created this extension as a fun project with an unserious name when I was a college student.

I can't imagine there are so many people who choose this small extension as their must-use-everyday tool. Till now (2021-07-22), there are more than 1.77M people installed this extension.

Back to the days I started to write this extension, I tried to make the extension have a similar appearance with Google's official mobile app to avoid too much learning cost for users who move from their smart phones to browsers. Though most users can use this extension without any pain point, the similar UI and generic name is a double-edged sword. We never try to mislead people to think this extension has any relationship with Google company, but some people do think this is a Google official production which can sync data from the Google's mobile app.

Renaming is a hard decision, especially there are millions of people who have recognized the name we are currently using.

Because we use authenticator.cc as our official website, some medium uses Authenticator.cc to reference the extension. I think Authenticator CC is an acceptable name, when I search "Authenticator CC" in Google, authenticator.cc is the first item in the list. If we must give a meaning to CC, I think we can say it stands for Credential Codes.

@mymindstorm how do you think of the proposal?

@mymindstorm
Copy link
Member

Sorry about not getting back to you on this sooner.

I agree with you on needing to change the name, especially after looking at our search console data:

Similar apps names usually share the same "<company name> Authenticator" format which we should take advantage of. Users will understand what the extension is more easily when keeping that format.

Regarding the specific suggestion, I don't think it escapes the problems that we are facing. We need to have something that ensures clarity over which "Authenticator" the extension is. I don't think that appending "CC" will solve that problem because it's fairly ambiguous.

We don't need to worry about search position as long as we keep the "Authenticator" part of the name intact, since our search impressions (to authenticator.cc) are mostly driven by that term as shown from the search console data. All we really need to do is pick an original (i.e. with little search presence already) proper noun to serve as a name and add "Authenticator" to it. Unfortunately, I don't have many ideas... Something that evokes the idea of defense/protected enclave?

Also, we need to have some redundancy in publishing access due to the large userbase in case one of us is unable to continue maintaining the extension. I am not suggesting any change to how we currently manage releases, just that we should have that access in place in the event that it is needed.

@mymindstorm
Copy link
Member

We should also reconsider the use of "for Google Authenticator" on the Chrome promo tile.

Screenshot from 2021-10-23 18-53-50

@Sneezry Sneezry closed this as completed Mar 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants