Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

Primary mentor

Rishabh Agarwal

Backup mentor

N/A

Assigned to

N/A

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.

Considering the services offered by a hospital, an Android application can help doctors, patients, and other staff a lot with its mobility and ease of use, without them having to start the OpenMRS web app on a desktop computer. This will improve the productivity and efficiency of the hospital workflow.

This year, we will work on making the Android client more extendable and implementing the offline first architecture in the app, the Android app must be extendable and easy for the implementers to deploy and implement, 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, and in addition,the Android app should integrate more of 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).

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.

Project Champions

Objectives

  1. Making the app easily extendable, i.e. Abstracting out common functionalities which almost all implementers would require into a jitpack library.
  2. Making a hello world module in android client using the jitpack library and document it.
  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 : Continue Migrating the remaining 80% codebase to kotlin.
  2. additional : Start converting MVP pattern to MVVM as it follows the new standard guideline brought by Google.
  3. additional : Re-design Home screen with a better UI.

Examples

  1. A doctor does not have access to a PC, but his Android phone is available to use during office hours.
  2. No internet connectivity and a doctor needs to work offline temporarily.

Skills Needed

  1. Android 
  2. Java
  3. Kotlin
  4. Jitpack libraries
  5. MVVM Architecture

Documentation

  1. The features added or modified must be documented in the hosted at OpenMRS client user guide with the github repository here.

Resources

  • No labels