petmongrels
commented
1 year ago Ashwini slowness issues
- Opening overdue list. Reason - displaying too many subjects on the screen.
- Opening a subject from the overdue list. Reason - it renders previous screen internally.
- Pressing edit on encounter/enrolment. Reason a) same as 2 b) display individual profile component multiple times c) due to display of radio/checkboxes
- Pressing next Reason a) same as 2 b) same as 3(b) c) same as 3(c)
JSCS slowness issues
- Opening of search screen Reason ? (not reproducible after batch 1 fix. probably fixed by it.)
- Searching based on all fields (this search is slow in because of the numbers of records in the mobile database)
- Edit registration details (due to the number of radio buttons)
- Pressing next in registration (same as ashwini 4)
Fixes Batch 1
- 1 (reduced the number of subjects form 45 to 15)
- 2 (fixed the router to not rerender the previous screen)
-
3b (internally partitioned IndividualProfile into two semantic components to not do unnecessary dispatches)
What to test
- most important to test is to check whether screen navigation works properly. Check across the app with all regular screen flows.
Fixes Batch 2
- 3c (This should also fix issues related to my dashboard and search filters)
Cannot fix immediately
- JSCS's issue of Search by All registration fields. There is a lot data on user's devices. This search goes across registration and enrolments. Upgrading realm version may fix this but it would take time.
mahalakshme
Ashwini
Ashwini reports that there is not much benefit for them. The organisation is finding it hard to convince users to use the app.
They have attached a video here Workflow - Go from dashboard to list of cards to an individual, try to edit an encounter.
JSCS
Form data entry is slow. This makes data entry hard. This is similar to multiple "overlapping screens" thing that was reported otherwise
https://avni.freshdesk.com/a/tickets/2378