add organization: url: attempt to autocomplete with zulipchat.com

[jtagcat]

Problem Description

Expected: overnode.zulipchat.org

Proposed Solution
If the entered string does:

• match the organization url conditions (Subdomain can only have lowercase letters, numbers, and dashes.)
  • (including) doesn't start with a protocol (https://overnode should still work)
  • (including) doesn't contain any dots, aka any TLDs.

If the URL will be autocompleted, Show that within the text box (with grey text?).

Describe alternatives you've considered
Give the user a first time impression of ERROR?

I might attempt to close this myself within tommorow - 3 months

[JulianGro]

The android app already does this. Just FYI.

[timabbott]

Thanks for the feedback! Yeah, I'd like to see this changed in the desktop app as well. We should be smart about the UX details around this though -- we want to make it very clear what URL users will be connecting to if they submit the form. One possible option would be to have two text boxes, with the top one being https://_____.zulipchat.com.

(I don't think the Android app's exact implementation on this is particularly good)

[akashnimare]

It make sense to autocomplete the url in the mobile app but in the desktop app, we should try to keep it as simple as possible. Don't need to add too much autocompletion and all. I think having two views (Self-hosted, zulipchat.com) would make sense here.

[jtagcat]

UX? One box, if the current text input matches the conditions, show <input placeholder=".zulipchat.com">-like thing, grey text at the right of the text input.

[timabbott]

Yeah, I think that's better. We can assume https unless the URL starts with http:// (support for which is mainly for testing with the development environment).

[abhigyank]

I think some selfhosted folks could have something like http://zulip defined for their internal network. In those cases it would break for them. The solution for that would be to have two input boxes. Perrsonally I feel it maybe confusing/bad UX.

[jtagcat]

As I mentioned before:
hosted → https://hosted.zulipchat.com
http://hosted → http://hosted
https://hosted → https://hosted

With http, you would need to type http:// anyways, as we can default to https://. I don't see the problem here.
Adding the gray .zulipchat.com appended when no protocol is found, and the instance name is compatible with the naming rules makes it even more clear?

How is this exactly handled in the mobile app? Did we miss something?

[timabbott]

Yeah, @jtagcat's comment reflects what I had in mind; I believe that's the algorithm the mobile app uses at a high level.

@gnprice FYI.

[Signior-X]

Are you still working on this? @aryanshridhar
or should I take it forward.