Skip to content

Remove hurdle of creating an account #1238

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

Closed
nicolas-raoul opened this issue Mar 2, 2018 · 22 comments
Closed

Remove hurdle of creating an account #1238

nicolas-raoul opened this issue Mar 2, 2018 · 22 comments

Comments

@nicolas-raoul
Copy link
Member

Google Play statistics suggests that a lot of people uninstall the app just after installing it.
I suspect that the biggest blocker is the login screen. Most people probably give up at that step.

Proposed solution: Allow people to browse Commons, and even upload pictures, without the hurdle of choosing a username and password.

The app could show: Log in with existing account / Create an account / Continue without an account

"Continue without an account" would actually create a random name and password, and store them in the app's local database.
Uninstalling the app would mean the account is lost forever. Or we could have a small dialog that shows the username/password that have been created.

I am not sure whether all of this is possible (for instance account creation might require solving a captcha which might be difficult to make the user solve), but it might be worth considering.

@knight-shade
Copy link
Contributor

knight-shade commented Mar 2, 2018

@nicolas-raoul Smart Lock might be just the right thing for this AFAIK.
https://developers.google.com/identity/smartlock-passwords/case-studies
What do you think @maskaravivek , @neslihanturan , @misaochan ?

@misaochan
Copy link
Member

I agree with allowing the user to browse Commons and view Nearby without having to be logged in.

A few concerns though:

  • I suspect doing this will require quite a thorough overhaul of many parts of the codebase? AFAIK our current (partially legacy).code is built on the assumption that the user is logged in. It will likely be a much larger task than it seems on the surface.
  • I'm not sure if allowing users to upload with throwaway accounts will be a popular addition from the perspective of Commons patrollers :)
  • Not sure if Smart Lock is compatible with WMF privacy policies

@nicolas-raoul
Copy link
Member Author

As tipped by @sivaraam we should probably do without the login screen, and directly show featured images and browsing to the user.

Then when the user tries to upload a picture we should popup the login screen.
We could also have a "Login" item in the navigation menu for people who want to login without uploading an image.

@ujjwalagrawal17
Copy link
Contributor

@nicolas-raoul @misaochan @neslihanturan @maskaravivek
The order in which I think skip feature should work is Welcome Screen will come in first run after that everytime explore activity will come if user is logged in or not. The drawer menu will changed if user is not logged in

@neslihanturan
Copy link
Collaborator

My opinion:
After welcome screen, Explore screen should come if user is not logged in. Otherwise (if user is logged in), Main screen (which will be Upload and Nearby soon) should be visible. Since the main function of our app is uploading.

@nicolas-raoul
Copy link
Member Author

Like Nes, I am in favour of keeping an upload-related activity (currently "My Uploads") as the default activity for logged-in users.
Everyone else what is your opinion?

@maskaravivek
Copy link
Member

I tried to conduct an informal survey at Wikimania to understand what would they like to see as soon as they enter the app. The opinions were divided, with many of the people wanting My Uploads activity as their home activity and many others were hoping for some explore commons feature(For them seeing their own uploads was not very useful). The sample space here is 15-20 people.

Given this dichotomy, we might consider giving this option to the users themselves. They could set the default landing page in settings. If Settings doesn't seem appropriate for this we can probably continue having My Uploads as the default activity for logged-in users as many people do find it useful. Personally, I as a user who doesn't upload many pictures would love to explore pictures uploaded by others.

@sivaraam
Copy link
Member

If Settings doesn't seem appropriate for this we can probably continue having My Uploads as the default activity for logged-in users as many people do find it useful.

I think giving the option to the user would result in us opening up the pandora box. It might very likely cause unwanted issues in the upcoming days.

Personally, I as a user who doesn't upload many pictures would love to explore pictures uploaded by others.

Me too (regardless of whether I'm not logged in/not).

I don't think @neslihanturan's statement "Since the main function of our app is uploading." would hold once the browsing and Explore feature have been added to the app. I anticipate a lot of users would be using the app for browsing. So, the app wouldn't be upload only anymore. Anyways, that's an anticipation!

To be honest, being a very in-frequent Commons app uploader: I never found the usefulness of the contributions screen! It shows the images I've uploaded which might be useful. But I don't think it's as useful as the browsing or Explore feature (I'm not even able to download the images I upload! #1216). That's me, anyway.

That said, I would be in favor of the app choosing the app the main screen rather than letting the user. It would be nice if we could have a survey with a wider audience. 15-20 people seems too low. The results are quite likely to vary for a wider audience.

@nicolas-raoul
Copy link
Member Author

nicolas-raoul commented Jul 28, 2018

I believe we should avoid proposing options unless really necessary, because:

  • It makes important options less visible
  • It multiplies the possibilities of bugs
  • It makes testing (and trying to reproduce crashes) take more time

I asked our Facebook community to comment here.

@misaochan
Copy link
Member

misaochan commented Jul 28, 2018

To answer @ujjwalagrawal17 's question specifically, I personally think that the best way to implement this for the time being is to:
(1) display tutorial first, always, then
(2) display login screen with a prominent option to "proceed without logging in". If they decide to do that, then
(3a) we can display the browse activity as the main screen, otherwise
(3b) if they login, we proceed to uploads as normal

This allows the feature to be implemented without needing us to make a decision so soon about whether to switch browse to the main screen for everyone or not. Some people strongly prefer being able to view their uploads immediately after every upload (AFAIK making browse the main activity would make users return to that after every upload as well, not just at the start, unless we want to devise a more complex activity flow). I personally am one of those people, as I want to see whether my last upload succeeded, what my last few uploads were so I don't repeat them (I tend to be forgetful, lol), and to jog my memory about what I have not uploaded yet.

@nicolas-raoul
Copy link
Member Author

nicolas-raoul commented Jul 28, 2018

@misaochan About step (2): It was the topic of #1238 (comment) in my understanding it has already been decided upon, and actually Ujjwal has implemented that way.

@misaochan
Copy link
Member

misaochan commented Jul 28, 2018

@nicolas-raoul But in that case wouldn't that make the decision for us that browse must be the main activity?

I apologize for missing @sivaraam 's comment on that PR, but my thoughts on it are that:

I suggest this way because, it's quite possible users wouldn't notice the ability to "Skip" the log-in. If a lot of people do miss it out then it's quite possible the amount of users who uninstall the app immediately after installing it wouldn't be reduced much (which I suppose is the one of the main goals of this PR).

This is true, but only because of the WAY that it was implemented in the PR. If we make it a prominent option, and not just say "skip" but rather "proceed without logging in", we can make it virtually impossible for the user to miss. For instance:

cc-reg-screen

@nicolas-raoul
Copy link
Member Author

@misaochan Once people log in, "My Uploads" becomes the home activity.

@misaochan
Copy link
Member

Hmm. In that case my only concern is that existing users would be surprised with the Browse screen and the lack of login screen (and since Browse currently looks a lot like Uploads, they may miss the title and wonder why they have such strange uploads now), but hopefully they will still try to upload anyway and be prompted to login.

It also raises the question of what we will do when #725 is implemented, which will be soon.

@ujjwalagrawal17
Copy link
Contributor

Yup now thinking again I also agree with @misaochan. We should make it like she is telling so that the current users (they are mainly uploaders) don't get totally disturbed. We can maybe change it later.

@nicolas-raoul
Copy link
Member Author

We don't have that many users right now, so I think it is OK to prioritize future users' experience :-)
@ujjwalagrawal17 don't you think it is a bit late to change that again? If you really feel that way please do like you want, and let us know as soon as it is ready to test.

@ujjwalagrawal17
Copy link
Contributor

Wikipedia app also directly shows explore page but they have a nice card for first time users which tells the advantages of login. One of the aim of Wikimedia Commons is to provide access to free usable images to everyone. Not just uploading. @misaochan if we delay it now then maybe it can be delayed for a long time. So I think we can skip the step you are saying and directly show explore as the main page for not logged in users.

@misaochan
Copy link
Member

misaochan commented Jul 28, 2018

IMO there is a big difference between the main aim of the Wikipedia app and the (current) main aim of the Commons app. The Wikipedia app is predominantly for reading, not editing. The Commons app is (to current users) mainly for uploading, not browsing. Things could certainly change in the future depending on the response to the Browse feature, but at the moment I really think we are not ready for Browse as the default main activity. At the very least, if we must do so, we should have a demo to walk users through it (here is the browse feature, it shows pictures uploaded by other people on Commons, you can still log in and upload here, when you log in you will be brought to your uploads, etc), which would take more time to implement IMO.

@nicolas-raoul Given that we don't know whether users actually prefer Browse or Uploads as the main UI, what is the benefit to future users of immediately having a browse screen instead of the usual login screen with a prominent "proceed without logging in" option? It seems to me that both would be equally useful for future users, whereas the latter would be more comfortable for existing users, so the net gain is higher.

I understand GSoC time constraints, but this is not a mandatory GSoC task, right? So Ujjwal can work on it as he likes, and if it's not ready by the time GSoC is over, there should be no problems?

@nicolas-raoul
Copy link
Member Author

With "Login" and "Upload" items in the navbar, I am sure existing users would not be lost.

I have no strong preference between the two, actually. It is just that there was a consensus and Ujjwal implemented it, so I feel bad about going back on this. But if Ujjwal is OK to implement as you say, I am totally OK with it :-)

Allowing non-logged-in users to browse is a mandatory GSoC task, scheduled "July 24 to July 30" at https://phabricator.wikimedia.org/T188597

@misaochan
Copy link
Member

misaochan commented Jul 28, 2018

Oh, okay! I guess if time is really an issue he can submit the PR first and we can alter the login flow later as needed. There is no GSoC requirement for it to actually be released to users, right? So we can release the current state of Browse first, and then leave the login/activity switch to a future decision.

@nicolas-raoul
Copy link
Member Author

Understood!

So, @ujjwalagrawal17 please decide whether you prefer to first show a login dialog or not, and implement it :-) Please tell us what you choose and then let us know when it is ready.

@ujjwalagrawal17
Copy link
Contributor

We can do it as @misaochan is saying it. I will update the PR accordingly and let you know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants