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 5 Next »

Primary mentor

Suarabh
Backup mentorRohit Sharma
Assigned to

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.

The potential goals for this year could be (but are not limited to) :

  1. An upgrade to the Architecture Model of the app. As Android apps grow in size, it's important to define an architecture that allows the app to scale, increases the app's robustness, and makes the app easier to test. The present architecture model of the app is MVP.  However, as Android now recommends using MVVP (Model View ViewModel) model as It can be integrated with the latest Architecture components. This indeed will reduce so much of the boilerplate code and will help newcomers to understand and contribute more to the Android client.
  2. Dependency Injections : Classes in the app depend on other classes in order to function properly. Android now recommends following dependency injection patterns and using the Hilt library in Android apps. This will help to automatically inject required classes' objects in the constructors. This indeed will again reduce the boilerplate code and makes the code more understandable and manageable.
  3. Testing: The status quo or the present test coverage status of the app is very low. There is a stack of classes which have had never been tested. Testing is an integral part of the app development process. More tests should be added to increase the test coverage of the project.
  4. Replace the remaining Java code with Kotlin. Both Java and Kotlin can be used to build performant, useful applications, but Google's libraries, tooling, documentation, and learning resources continue to embrace a Kotlin-first approach; making it the better language for Android today.

Objectives :

  1. Upgrade MVP model to MVVP
  2. Use Dependency Injections
  3. Increase Test Coverage
  4. Migrate Java classes to Kotlin
  5. Integrate more components of the web app to the client (to be discussed further)

Project Rating and length

Medium

175 hours

Skills Needed :

  1. Android 
  2. Java
  3. Kotlin
  4. MVVM Architecture
  5. JUnit Testing
  6. Architecture Components
  7. Android Jetpack Libraries

Resources :

  • No labels