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 Page History

« Previous Version 17 Next »

Primary mentor

Fawwaz Yusran

Backup mentors

CLIFF GITA Vibhor Chinda

Assigned to

Rishabh Agarwal 


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 focus on two aspects to improve the Android client - performance and UI/UX.

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. Also, 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.

Next, the current user interface is slow to respond to user inputs and does not look pleasing to the eye, compared to the newer and modern Android apps in the google play store. E.g. 'Undo' buttons (that takes the user back to the previous state if he/she errors) should be available for any operation. So we should enhance the feel of the app so that the user knows that he/she is in control every time.

Finally, seeing the number of components in the webapp, the Android app should integrate more of them so that doctors and staff can expect to see the same functionalities in the webapp implemented in the client.

An additional request is to migrate the Java source code to Android's now recommended Kotlin, to increase readability and reduce the the thousand lines of code present in the GitHub repository.

Objectives

  1. Material UI design
  2. integrate more components of the webapp to the client (to be discussed further)
  3. Password reset via email
  4. Replace Java code with Kotlin

Sample Use Cases

  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.

First Tasks

There are a Ready to Work issues to get started on:

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Project Champions

Same people who use the webapp: Providers (e.g. doctors, nurses, clinicians)

Skills Needed

Android, Java, Room, Kotlin

Dev Tracks

Resources


  • No labels