account creation (setup): refine explaining text and wording

Your encryption key, might be even better

I dont' understand what you mean. Could you please elaborate a little?

"for importing and exporting..." maybe better use encryption key, that might alert ppl, like me. I lost my account cause I didn't know I deleted my key when I reinstalled the app

changed the description

I changed the text above. Ok?

Looks great :)

added UI or UX label

The password is used to protect the account's archive on this specific device. It's used anytime Ring needs to decrypt the archive.

password for device export/import or backup of your account setup (incl. the secret key) is too long I think, but this point is important. I'm not sure on what will be the best. A lot of things should have a really long explanation (i.e. usernames) for the user because it's different from another software...

What about an icon which by onmouse shows a dialog with all the info?

Yeah or a tip in a start up tip box to explain Ring (For a desktop client for example).

But does users read tips or on mouse dialogs?

Is the password saved on the device? It seems so, because there is not prompt after rebooting? Then I don't quite understand why the user needs to specify one. Maybe presenting a (longer) pin (passphrase) before the export would suffice?

A lot of things should have a really long explanation (i.e. usernames)

Yea, I actually usually remove an app again after seeing a wizard that requires to create an "account" somewhere...

What about: (moved to top)

The password is not stored anywhere.

The device certificate is accessible without a password, but the private key of the account is only accessible by decrypting the archive.

Users do not need to specify any account password, the pin entropy suffice and has enough entropy.

Ok, the background is the difference between device cert and account key.

pin entropy suffice and has enough entropy

If that's the case, then maybe default to create new account keys without a password? And have the generated pin for account key transfer and require to supply a password for account export into a file?

@ringthing @Nixim

When creating an account the info says "password to protect your account".

Changing it to something like "password for device export/import or backup of your account setup (incl. the secret key)" may provide a more proper reason.

You can contribute to translation at https://www.transifex.com/savoirfairelinux/ring/.

There are also ongoing work on a new user friendly in app tutorial at https://git.ring.cx/savoirfairelinux/ring-project/wikis/tutorials/Tutorial-in-app-(en)

added good first bug S - Ordinary priority4 labels

changed the description

With the proper explanations in the setup wizard, and under transfer/export (possibly buttons with further info), I think there should really be no need for an in-app-tutorial, here. Better not to need one for the basic things. :)

The "dht proxy" should just be on "auto", enabled automatically on mobile networks (data), and mobile devices (battery). (An explanation along with the setting is good, but not needed for basic usage.)

Is the text of the creation wizard accessible in some central repository (for all clients)?

No

Note that dhtproxy is still experimental, so not enabled by default

Well ok, I already made a couple of updates, maintaining the draft in the black text box in the comment above.

dhtproxy: Yea, not sure how much sense a dht node makes on mobile devices, but ok for TV.

changed title from account creation: password for account export/import to account creation (setup): refine explaining

changed the description

Can't edit the tutorial wiki myself https://git.ring.cx/savoirfairelinux/ring-project/wikis/tutorials/Tutorial-in-app-(en)

Please note there that with proper text in the setup wizard (take the text above in this issue as a starter) basic users really shouldn't need any tutorial, and just pointing to a wiki documentation seems like a good thing for advanced users.

changed the description

mentioned in commit 378c3864

assigned to @aberaud

Just tried Ring/Jami for the first time ... my advice/thoughts below. I'm not a totally inexperienced user, tried already: briar, tox, gajim, riot, conversations, threema, ...

Setting up my ring/jami Account (gnome client) made me think. I didn't really know what I was doing at first. Now after reading issues on gitlab I somewhat know. 'Normal' users cannot be expected to have the same persistence in trying to use Jami.

More important than it seems

If Jami wants to attract 'normal' users and not repel them, it is IMO absolutely essential that setting up the account doesn't pose questions that stay unanswered unless people read up on the net. I think this issue can't be estimated too important, if the aim is to attract more users. To me trying out a new messenger always has been like a process of probing forward to see where (which funtionality) the issue comes that finally makes it impossible or too much of a hassle to use the messenger. You don't want to loose potential users as early as account creation.

What to do

So every client needs to explain either with text right next to the fields or with tooltips what exactly each field means/implies. And it needs to explain it in a fashion that non-techy people understand.

My suggestions for the draft at the top:

* Register a human readable (nick) name in the public Ring directory 
  that will point to your RingID
  (recommended, but nicks can currently not be changed nor deleted)

"human readable" ... I'd omit that. It might confuse users. Almost everyone out there would anyways think of a (nick) name as something human readable.
There should be an info that it's unique and an explanation that an entered name might already be chosen by someone else. Not just the field turning red. Users will wonder whether it's taken or too short or not properly formatted. There also needs to be an explanation about case (in)sensitivity and what characters are allowed.
"point to your RingID" ... I think not everyone out there would get what's meant by that. I'd rather put it:

"Optionally you can register a (nick) name in the Ring directory. You can give it to other users so they can ask to connect with you. It has to be unique (like the RingID is) and its purpose is to be easier to use/remember than the long string of random characters that is the RingID itself."

I'd leave out the word "public" here. Users might think it reveals anything, makes something public. But it's not like a phonebook, since noone can easily browse the directory of nick names like a phonebook, or can they?
"recommended" ... I'd explain the implications more in detail. What if you don't choose to pick a nick name? Then how will you be able to let others connect with you?

The profile name.

There should be an info about the profile name.

That it's independent from the nick name
That it can be changed
What kinds of characters are allowed
Is it shown to other users?
Is it specified separately for each device?

assigned to @sblin and unassigned @aberaud

changed the description

Thanks Egon! I tried to integrate your points into the summary above.

changed the description

An additional problem with the wizard seems to be that it shows a switch to "use push notifications", even in the f-droid version.

Maybe that setting can be removed, and just be left to the default. (Off in f-droid builds, and maybe even in all builds once the dht/dhtproxy background operation works reliably https://git.ring.cx/savoirfairelinux/ring-client-android/issues/552.)

changed the description

mentioned in issue #596 (closed)

changed title from account creation (setup): refine explaining to account creation (setup): refine explaining text and wording

changed the description

For me this is the biggest obstacle to using Jami.

I've been gently trying for most of a year to persuade someone to

hit CTRL-ALT-T
type "apt-get install jami"
launch jami
type a nick in "Profile name"
skip all the other fields by hitting "next"
type my registered nick to talk to me.

This being a minimal functional install on Ubuntu, and really, it's hard to see how you could make it easier.

What is needed is not making it easier, but clearer and more reassuring.

Online documentation to make it easy for a potential user to visualize installing Jami.
- Tutorial plus screenshots (as very roughly drafted at #846 (closed)).
- Socially, this is a link you can send to someone to show them how easy it will be.
Indicating that all of the fields in the "Account" box are optional, and that you can come back and fill them in later.
- Relax! You are not making an irrevocable decision (on the basis on incomplete data).
- "Skip the complex stuff until you understand it" might be a good default order.
  - So, say, have the splash screen saying "This is your Jami username. Copy and share it with your friends!" contain a button saying "Generate a shorter, human-readable username, and link it to this 40-character address in in Jami.org's public address book". This allows you to reduce the setup to "Profile name" and "Password (optional)".
"Profile name" and "Username" is confusing. No new user will be clear on the distinction without hunting down external documentation. Rename. "Local nickname" and "Public Jami address"? "SuperChatty@jami.org" makes the analogy with e-mail addresses instantly obvious.
having information, explaining what the fields on the setup screen are, on the setup screen.
- tooltips or information-icon () links
- brief descriptions:
  - "Profile name: Mandatory. Whatever name your friends will recognize. Does not need to be unique."
    - judging by the number of "john865"-type profile names, a lot of people do not realize that profile names need not be unique
    - maybe call the "profile name" a "local nickname" instead
  - "Address-book username: Optional. A more memorable Jami address (default is a randomly-generated 40-character word). Registering the username puts it in a public database, linked to the 40-character word, so your friends can find you using the name instead. Must be unique."
  - "Password: Optional. Protects your Jami account from anyone who has access to your computer. Warning: Your account details are only stored on your computer(s). If you forget you password, your account is irretrievably lost."
The buttons that say "Create Jami account" and "Link this device to an account" should maybe say something like "Create Jami account (new users start here)" "Link this device to an existing Jami account", so that it's clearer that new users want the first option.

Even very simple installs and updates are a seriously scary process for some people. I do not say this fear is logical, but it is a real obstacle to my using Jami. From my point of view, ease of entry is the key functionality that Jami is missing.