Versions Compared

Version Old Version 6 New Version Current
Changes made by

Saurabh Kumar

Saurabh Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Primary mentor

Rishabh Agarwal

Backup mentor

N/AJuliet Wamalwa

Assigned to

N/ASaurabh Kumar

Abstract

The goal of the Android client is to provide an alternative to access a hospital's OpenMRS instance by just using the provider's Android devices. See the full Android client guide for more info.

...

This year, we will work on making the Android client more extendable and implementing the offline first architecture in the app.The , the Android app must be extendable and easy for the implementers to deploy and implement by encapsulating common functionalities of the app using Jitpack library, so that the android client is properly utilized and really solves some heathcare problems. 

The offline-first solution needs to be developed and extended further, where a provider cannot connect to the internet and needs to work offline temporarily. Data should be synced again when back online.

Moreover, there are still frequent crashes when using the app, especially if a doctor is using it for a long time with no pause. On crashes, the app will just return the user to the dashboard page, and any unsaved transactions will be lost.Finally, seeing the number of components in the web app, the Android app should integrate more of them the features of the refapp so that doctors and staff can expect to see the same functionalities in the web app implemented in the client (To be discussed further).offline-first solution needs to be developed, where a provider cannot connect to the internet and needs to work offline temporarily. Data should be synced again when back online. An additional request is to migrate the Java source code to Android's now recommended Kotlin, to increase readability and reduce a thousand lines of code present in the GitHub repository.

...

  1. Making the app easily extendable, i.e. Abstracting out common functionalities which almost all implementers would require into a jitpack library, for detailed information this Talk post might be useful which presents the problem which we want to solve by making the app more easily extendable for the implementers.
  2. Making Creating a small module ( lets say hello world module in android client using the jitpack library and document it.), Using the encapsulated library depicting clearly how to use that jitapack library from scratch, for e.g. the module could be anything like fetching the list of patients or providers.  
  3. Implementing a robust offline structure for the various functionalities of the app (which covers currently only the provider module).
  4. Make the app more stable and reduce crashes checking backward compatibility issues testing on lower API devices.
  5. Integrate more components of the web app to the client (to be discussed further).

Extra Credits

  1. additional Additional : Continue Migrating the remaining 80% codebase to kotlin.
  2. additional Additional : Start converting MVP pattern to MVVM as it follows the new standard guideline brought by Google.
  3. additional Additional : Re-design Home screen with a better UI.

...

  1. The features added or modified must be documented in the hosted at OpenMRS client user guide with the github repository here.
  2. Getting Started with openmrs-android-sdk - documentation created for openmrs-android-sdk introduction.

Detailed Project Report

Weekly Reports

Outstanding work 

  1. Integrating more modules into the client.
  2. UI overhaul (Need some work on the already opened PR here)

Final Presentation

  1. Talk post - Link
  2. Presentation Video - Link

Resources