Registration Screen

UI and UX
1

As we’ve seen from feedback in Liberia, many users have problems completing the registration screen (especially those not used to entering passwords, being case-sensitive etc). On the other side there are difficulties in then being able to identify who is a ‘real’ user vs someone who has just installed the app for testing/demo - especially when trying to do any data analysis.

There is also a need to record a location for a user - might be region/county/district/facility - or whatever terminology is used in the particular implementation.

To simplify this, specifically for the LMH Liberia implementation at first (though we may look at a more generic version to put in the core app), my suggestion would be to have the registration screen as a series of pages, as follows:

  • Screen 1: Select your role: (from CHA/CHSS/Other). If the user selects other, then it goes to the existing registration screen; otherwise:
  • Screen 2: Enter firstname/lastname and employee no
  • Screen 3: Enter password
  • Screen 4: Select county/district from drop down lists

The user then does not need to create an Oppia username, as it can be auto generated from their name & employee id.

The only issue I can see specifically for the LMH Liberia implementation is that it’s not going to account for all the users who have already created accounts and have registered, so there will still be a need to find out and enter the role and location for the existing users.

Any feedback/thoughts welcome,

Cheers,
Alex

2

Something like a “profile” menu on the Navigation drawer can help in this case, and through this profile , the users can update, their information. For the already existing users, they can all be assigned a default role, and then update their own roles by editing their profiles.

3

Hi @hakimks,
A couple of updates for you on this:

  1. On the server, we added the option of adding custom user profile fields (see: https://github.com/DigitalCampus/django-oppia/issues/682). So these can be added just in django admin and will be enforced when someone registers (via the server form or the api) - so hopefully avoids the need of projects needing to add custom code for adding new fields
  2. There is also now an API endpoint on the server to users to update their profile (see: https://github.com/DigitalCampus/django-oppia/issues/687)

At the moment this is all just on the server side, but in our next sprint (in Jan) we’ll add the option to edit the profile from the app (see: https://github.com/DigitalCampus/oppia-mobile-android/issues/934) - though note that in this first development of this, users will need to be online to update their profile.

Cheers,
Alex

2 Likes
4

Thanks , let me check this out