2 added 24 characters in body
source | link

If the primary task for user is to create custom URL and

What I'm worried about is that users won't be able to tell that Custom URL is an editable field

then:

  1. Make this field first, not the last, as it's primary task.
  2. Make it autofocused.
  3. If you already have some info onfrom user (name, email), set initial field value as user name, not the dummy newaccount. Smart defaults!

If the primary task for user is to create custom URL and

What I'm worried about is that users won't be able to tell that Custom URL is an editable field

then:

  1. Make this field first, not the last, as it's primary task.
  2. Make it autofocused.
  3. If you have some info on user, set initial field value as user name, not the dummy newaccount. Smart defaults!

If the primary task for user is to create custom URL and

What I'm worried about is that users won't be able to tell that Custom URL is an editable field

then:

  1. Make this field first, not the last, as it's primary task.
  2. Make it autofocused.
  3. If you already have some info from user (name, email), set initial field value as user name, not the dummy newaccount. Smart defaults!
1
source | link

If the primary task for user is to create custom URL and

What I'm worried about is that users won't be able to tell that Custom URL is an editable field

then:

  1. Make this field first, not the last, as it's primary task.
  2. Make it autofocused.
  3. If you have some info on user, set initial field value as user name, not the dummy newaccount. Smart defaults!