Ios: [UX] Registration should allow bare hostnames, not require protocol

Created on 27 Jan 2017  路  8Comments  路  Source: nextcloud/ios

During account setup, the iOS client for Nextcloud asks for a URL. If the user types just the hostname (e.g., cloud.example.org), then they are told "unsupported URL" and the field is cleared.

Multiple changes to the UX could be done here:

  • Nextcloud/iOS should detect no protocol in the URL and try https, first, then http.
  • In the case that the hostname is wrong, leave the hostname in the field for the user to edit. It's more likely they misspelled it or used the wrong TLD (.com instead of .org).
  • The URL field could also be pre-filled with https:// when the user selects the empty field.
  • The error message should specify "The URL should start with http:// or https://"
  • The field should use the URL keyboard.
1. to develop bug good first issue

All 8 comments

@jlfranklin Thanks for your help !

@jlfranklin exactly, it should be automatic! These are the tasks:

  • [ ] Nextcloud/iOS should detect no protocol in the URL and try https, first, then http.
  • [ ] In the case that the hostname is wrong, leave the hostname in the field for the user to edit. It's more likely they misspelled it or used the wrong TLD (.com instead of .org).
  • [ ] The field should use the URL keyboard.

@nextcloud/ios this is an important first run UX fix.

@marinofaggiana I have fixed this issue. See pull request #96. But still the issue in open state

@tapanprakasht awesome, thank you for your contribution! :) Looking forward to more from you.

The only thing left is setting the hostname field to use the URL keyboard.

@jlfranklin Would you mind to file out separate issue for keyboard?

Sure. Added as #158.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MorrisJobke picture MorrisJobke  路  4Comments

marinofaggiana picture marinofaggiana  路  5Comments

jancborchardt picture jancborchardt  路  5Comments

AxelGard picture AxelGard  路  4Comments

MarcusE1W picture MarcusE1W  路  5Comments