Dual Phrasing for Connected Accounts' Buttons

frm

Well-known member
It would be nice if we could have dual phrases for connected accounts' button.

This is the macro used for both login and register, and an example of it with X:
HTML:
                                <xf:macro id="connected_account_macros::button"
                                    arg-provider="{$provider}" />

X is barely noticeable, and it doesn't give the user much of a hint of what it does on the login page or registration page.

On sign up:

1741024357691.webp

On log in:

1741024421499.webp

I tried to edit them to appear like:

1741024543844.webp

1741024480989.webp

But, this will completely break the button:
HTML:
                                <xf:macro id="connected_account_macros::button"
                                    arg-provider="Register using {$provider}" />

There has to be a better method to explain what the buttons do, at least with X...

A new phrase login_with and register_with (example of login_with) so that they can remain blank for how it is now and be used with both RTL/LTR buttons if we want a more informative connected account button?
HTML:
                                <xf:macro id="connected_account_macros::button"
                                    arg-provider="{{ phrase('login_with') }}{$provider}" />
<!-- AND -->
                                <xf:macro id="connected_account_macros::button"
                                    arg-provider="{$provider}{{ phrase('login_with') }}" />

Or perhaps even a title overlay for what [[X] X] means so you get some insight on the button when you hover it? (Not helpful for mobile, but it's something)...
 
Upvote 1
I’m confused.

How is “Login using: X” or “Register faster using: X” not already clear enough as it is?

Why is it clear for e.g. Google but not for X, as implied?

Is it because X is a stupid brand name? That sounds plausible but not an issue I care enough about given it’s a stupid decision made by someone who is allegedly intelligent.

You may want to consider changing the phrase used for the X connected account provider. You could change it to “X (Twitter)” if you feel that would be clearer. Or “Twitter (Elon’s version)” or something. Or if I’m being less obtuse maybe “X.com”
 
How is “Login using: X” or “Register faster using: X” not already clear enough as it is?
None of them are clear enough; X is the only one I have. Otherwise, I would've wrapped Login with Google and Register with Google for clarity on it too.

But, of course
A new phrase login_with and register_with (example of login_with) so that they can remain blank

The two phrases could be shipped blank, and it be Facebook/Google/etc. out of the box. Or, users could revert by making them blank.

But for clarity's sake, they can be populated to make the button's action a lot clearer.

1741043032411.webp

Even though it's "clear" that you are registering faster using X, it's not as prominent as it would be in the button, or with a tooltip, of what you are doing.. The second option to the suggestion would make a sub-row for "Register faster using" and it state something, "Use one of your accounts listed to 1-click sign up/log in to Board title" (or something more concise).

I tried to do a quick mockup with formRow-explain, and instead of phrases login_with and login_using, use a phrase that explains the buttons better as a group.

1741043553244.webp

Since editing the macro breaks the button, I'll probably go this route to until something can be settled, because to me even as an admin, the action of the button is still unclear, even after taking the time to set up a connected account app and integrate it.

You may want to consider changing the phrase used for the X connected account provider. You could change it to “X (Twitter)” if you feel that would be clearer. Or “Twitter (Elon’s version)” or something. Or if I’m being less obtuse maybe “X.com”
That still doesn't solve the problem on /login or /register because the button is just a button of X.com or even Magic Doodle Company.

What's the button's purpose on those two pages?

You can make it clearer that on /login populated with "Login using" (login_with) and /register populated with "Register using" what Login using Magic Doodle Company and Register using Magic Doodle Company does respectively. Also, you can have a tooltip overlay (title=) that expands on what the functionality does, i.e., "By clicking here, you will be logged in/registered to this site by using your Magic Doodle Company account."
 
Last edited:
Back
Top Bottom