/
Android Reg Client workshop day #1

This space contains discussion itinerary for day #1.

  1. Present the entire feature list- 20min

  2. Discuss the feature flow (any deviation from existing Reg Client?)- 30min

    1. New Registration

    2. Update

    3. Lost

    4. Operator onboarding


  1. New feature ideas:- 120 min

    1. From resident’s perspective- 40min

    2. From Operator/Supervisor perspective- 40min

    3. From country’s perspective?- 40min

  2. Strategy for documentation (docs/sub domain of docs)- 10min


Existing features of Registration Client

Registration Tasks:

  1. New-registration: Fresh registration of applicant PHASE I

  2. Lost UIN: The resident has lost his UIN

  3. Update UIN: The resident wants to update his demographic data/documents/biometric data.

  4. Applicant Biometric Update: The applicant wants to update his biometrics since the biometrics that was captured did not cross the threshold.


Operational Tasks:

  1. Synchronise Data: Triggers all the sync/scheduled batch jobs

  2. Download Pre-registration data: The Operator enters the AID and the applicant data is pre-filled.

  3. Update Operator's Biometrics: When there is a need to update Operator’s Biometrics.

  4. Application Upload: To see the status of the applications

    1. To be uploaded

    2. Uploading

    3. Uploaded

  5. Center Remap Sync: when the machine is remapped to a different center, that sync happens when "Center Remap Sync" is clicked

  6. Check Updates: For any software version upgrade


Ancillary features:

  1. Profile Icon: Gives details about the operator

    1. Photo of Operator

    2. Username of Operator

    3. Last login details

  2. Audit: Auditing the events being performed

  3. Forgot Password: When the Operator has forgotten his password and wants to set a new password

  4. Help Section: This section will contain FAQs, quick help guide

  5. Multi Lingual Support: Ability to support multiple languages

    1. Transliteration for each input field

    2. Language specific keyboard

  6. Display machine name and center: Fetching Trust keys that will help to register the device

  7. Reset Password: When the Operator knows his password and wants to reset his password.

  8. Bell-icon notification: To get notifications…..TBD

    1. System/device notifications (offline)

      1. No space (administrative control)

      2. Sync did not happen since…..

      3. Battery %

    2. Admin generated (online):

      1. Holidays

      2. Version upgrade

      3. Reinstall SDK driver

  9. Dashboard: To view statistics such as:

    1. Number of packets created

    2. Number of packets uploaded…etc.

  10. Settings:

    1. Scheduled Job Settings - Shows the list of all the jobs, their cron expression, their last run time, next run time. We can individually and manually trigger any job from this section.

      1. Next run

      2. Last run

    2. Global Config Settings (and shortcut)- List of all the configurations (some can be edited-local value ones).

    3. Device Settings - Displays the connected devices, intent based (diagnostic)

  11. Telemetry

    1. Time spent on each page

    2. Version

    3. Average time of usage


New Features for Android Reg Client

S. No

Perspective

 Feature proposal


1

As a resident

Ability to verify my email Id or phone number on the go-

-The resident sends the SMS (OTP)

-SMS cost in Africa?

-Send link and verify yourself (fill basic info)

P3

2

 As a Resident and as an Operator (Resident Feature)

Resident: USSD service to book an appointment-

  1. New enrolment

  2. Update UIN

Operator: Get notifications for the USSD service.

X

3

 As a Resident

Resident: Hand over the UIN card on the go- after the registration is successful and packet is uploaded.

P2

4

As an Operator/Supervisor

Pre-Registration QR Code Reader with Registration Client X

X

5

As an Operator/Supervisor

Revamped master data synchronization to registration client- MOSIP-20658 X

X

6

As an Operator/Supervisor

Registration Client Dashboard Modification -MOSIP-24342

P3

7

As an Operator/Supervisor

Modify machine-center remapping- MOSIP-24326 - Multiple centers

P2

8

As an Operator/Supervisor

Support for multiple threshold values based on age and gender. Like Fingerprints, Iris and Face (based on resident age) since for some minors and senior citizen residents, capturing biometrics is very difficult.

A logic has to be in place to identify the threshold based on age and gender.

Reg Client feature-P2

9

As an Operator/Supervisor

Ability to hide/show password being entered at the time of login

P3

10

As an Operator/Supervisor

Ability to show the caps lock status for password at the time of login

X

11

As an Operator/Supervisor

Scan AID information and auto fill the form using pre-reg info

Populate the AID (Since AID is already in the system)

Remove “fetch data” since we know the length of AID (validate from that and auto submit)

P3

12

 As an Operator/Supervisor

Scan information from other document (OCR scan)

P3

13

 As an Operator/Supervisor

Pause and resume: Should be able to start filling the form where I left from

P4

14

 As an Operator/Supervisor

Get notified for children turning 5

X

15

 As an Operator/Supervisor

Capture the longitude and latitude of the address (based on current location) if address is not available

Along with latitude and longitude, Capture the photo of the house if in case address is not available

Should be able to plugin any address/location translation for e.g.: WHAT3WORDS

P3


As an Operator/Supervisor

Average registrations on a day

Exceptions done

Quality of biometrics throughout the day (graph)-Resident and as an Operator/Supervisor

P3

16

As a country

I would want to know the following:

  1. Number of registrations on each day of the week

  2. Number of male/female/others registrations

  3. Number of child/adult registrations

  4. Average time taken for a completion of registration

x

17

As a country

  1. Total live UIN

  2. Authentications/eKYC performed

  3. State-wise live UIN

  4. Data on the basis of age and genderData on the basis of day/month/year

  5. Data on the basis of kind of registration- registration center based and tablet based

x

18


Ability to export packets


19

 

 Usability Issues


20


Connected devices


21


The number of times the biometrics is captured


22


Pre-reg data sync as part of center sync Emoji :question_mark:


23


Device settings- how to handle if there is only one connecting port (how to toggle between hardware devices?)


24


Add peripherals to the tablet to make the experience better??


25


Machine level statistics:

  1. Quality metrics throughout the day

  2. Sync information


Operator level statistics:

  1. Average time for new registration for adults and senior citizens



Phase

Feature


Phase I

  1. New Registration

    1. Auto upload

    2. Conditional data

    3. Print feature

    4. Transliteration

    5. Packet size remains same as Reg Client

  2. Audit

  3. Logging

  4. 1.1.5 compatible

  5. Usability fixes - Identify

  6. Portrait mode

  1. Audit

  2. Logging

  3. 1.1.5 compatible

  4. Usability fixes - Identify

  5. Portrait mode


Usability issues

-Open source code to scan the texts/documents

-Keyboard usability

-How should the system behave

-E..g: Lock camera before taking the photo

-Input boxes alignment

-Document upload

-fundamental user guide (UI- design principles)

-Hand shaking issues (vendors)

-Dim light issues

-Config to make the solution fit the tablet

-Photo capture standard- ICAO (P?)



-Language specific keyboard

-Battery

-Brightness

-fonts( User should be able to choose the font size, type, weight etc.)

-Accessibility (zoom in, zoom out, pinch in, pinch out, three finger tap, 2 fingers tap etc.)

Management

Device management

-Data that we are sending and receiving

-Device space management

-Size of images/documents

Settings:

Support SD card and external devices?

-Center (should a device be mapped to a center/zone?)

Operator

-Supervisor- Do we need this role except for biometric exceptions? How to implement this?

-Configure it to be only wifi or wifi/cellular (upload of packet)