Client: Onboarding: opening non-aragonid.eth orgs from welcome screen is confusing

[john-light]

Describe the bug
Only organizations that use an aragonid.eth TLD can be opened from the welcome screen.

Mainnet or testnet?
Both

Expected behavior
I expect to be able to enter another ENS TLD (or Ethereum address) to open an organization.

Screenshots

[sohkai]

:smile: cc @bpierre clearly our clever UX solution was not obvious enough.

@john-light If you try to type something like governance.aragonpm.eth, you'll see that the .aragonid.eth part is removed.

Perhaps we can add a small subtitle or tooltip here to explain this? cc @dizzypaty

[bpierre]

As a note, I think we should also remove the .aragonid.eth part when users paste an address here.

[john-light]

I prefer removing the pre-filled .aragonid.eth part altogether. I think showing .aragonid.eth and then having it disappear if a user enters a different TLD still feels like it could be confusing even with a tooltip.

fwiw the way Gmail does it (using that as an example because it is a popular app and supports logging in with multiple domain names) they don't show @gmail.com when logging into Gmail, but if a user enters an email address pre-fix without the @ and domain name, then Google will assume they mean @gmail.com. So I could enter john-light on their login page and the next page will prompt me to enter the password for [email protected]. Whereas if I were to enter [email protected] then I would be prompted to enter the password for [email protected].

While my personal preference would be to require users to enter their full name every time (to get them used to seeing and typing this as the full name) this way Gmail does it could be a happy medium for the folks who like defaulting to aragonid.eth.