Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rephrase login dialog as most users do not own/control the server #3693

Closed
rasos opened this issue Aug 20, 2021 · 5 comments · Fixed by #4637
Closed

Rephrase login dialog as most users do not own/control the server #3693

rasos opened this issue Aug 20, 2021 · 5 comments · Fixed by #4637
Assignees
Labels
bug confirmed bug approved by the team

Comments

@rasos
Copy link

rasos commented Aug 20, 2021

The option Login to your Nextcloud should be rephrased to Login to a Nextcloud.

Most users do not host the nextcloud by themselves, but rely on a service partner or their company / organisation they work for. So it is not the user's nextcloud. We are having frequent confusions of customers and their partners / staff that want to sign up which option to choose, as none is really matching their use case:

Screenshot_2021-08-20_11-33-33

Login to your Nextcloud is probably only clear for admins.

#3011

Nextcloud Desktop Client Version 3.2.4 (Ubuntu)

@rasos rasos added the bug label Aug 20, 2021
@FlexW
Copy link

FlexW commented Aug 20, 2021

@jancborchardt @nimisha-vijay opinion please :)

@rasos
Copy link
Author

rasos commented Aug 25, 2021

Yesterday we probably lost a potential user of our nextcloud. He was already testing our nextcloud with the browser. When installing the App he erroneously clicked on "Create account with Provider" and found one who was slightly cheaper (but does not offer BBB integrated - so a lot to explain).

The second option in the login dialog should thus be probably rephrased to "Looking for a Nextcloud service provider?"

And the third option is also confusing to normal users (who don't really know what hosting means). Proposal for rephrasing: "How to install and run your own Nextcloud server".

I am not against competition among providers. But let us guide users who just want to sign in pave a more clear way. I would suggest that the first option should be highlighted for the most common use case which is that a user already has signed in via a web interface at his company / organisation and now is trying to add sync capabilities.

@nimishavijay
Copy link
Member

nimishavijay commented Aug 25, 2021

Pretty interesting!
For normal users, don't you think "your Nextcloud" would simply mean the one they use -- regardless of whether it is selfhosted or with a provider? My guess here is that the confusion arises because there is another option that explicitly states "Provider", so people are confused as to what the other one means now.

What if we kept the login option the same, and changed the second and third one?

  • Log in to your Nextcloud
  • Sign up for an account
  • Set up your own Nextcloud server

Agreed that the login option should be more highlighted than it is now.
What do you think?

@jancborchardt
Copy link
Member

Something that we can do wording-wise is to adjust it to be the same cross-platform. It’s quite nice how it’s done on Android, ref @tobiasKaminsky:
Talk wording
What do you think @FlexW?

Also @rasos to have the least potential of confusion for your customers, we recommend getting branded Nextcloud clients: https://nextcloud.com/branding/
This way your provider domain will be hardcoded and people will just directly be able to log in with username and password.

@tobiasKaminsky
Copy link
Member

tobiasKaminsky commented Aug 26, 2021

I like the idea to have it like Android (no I am not biased 🤣).
@jancborchardt can you take care that Talk clients then also do it this way?

I opened one for iOS: nextcloud/ios#1680
Would also be good to have it the exact same way: with log in button, "slide show"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed bug approved by the team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants