Page Comparison

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.

...

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 MVVPMVVM(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 that 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)Migrate the architecture of the app from MVP to MVVM.
6. Integrate dependency injection using Hilt.
7. Migrate the remaining codebase from Java to Kotlin.
8. Increase test coverage in the project.
9. Make the app more stable, and reduce bugs and crashes.

Project Rating and length

Medium

175 350 hours

Skills Needed :

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

Completed Objectives:

1. Migrate the architecture of the app from MVP to MVVM.
2. Integrate dependency injection using Hilt.
3. Migrate codebase from Java to Kotlin. (Completed 60% of the codebase)
4. Make the app more stable, and reduce bugs and crashes.

Remaining Objectives:

1. Migrate codebase from Java to Kotlin. (The remaining 40% of the codebase)
2. Increase test coverage in the project.

Project Final Report: https://github.com/amrsalah3/GSoC22-OpenMRS/edit/main/README.md

Project Final Presentation Video: https://drive.google.com/file/d/1JEWYtm7teTkSrFvExKU68obWo2rqqJ0q

Contributions & Work Done

Week 1

Week 2-3-4

Week 5

Week 6-7-8

Week 9

Week 10-11

Week 12

Week 13

Week 14

Week 15

Week 16

Week 17

Week 18

Week 19

Week 20

Week 21

Week 22

Weekly Blogs (Updates)

Resources :

• https://github.com/openmrs/openmrs-contrib-android-client/releases/tag/v3.0.0 - Release page for the 3.0.0 version.
• GSoC 2021 : OpenMRS Android Client Project 3.0.x - Previous year's GSoC page for this project
• https://github.com/openmrs/openmrs-contrib-android-client - main repo
• https://openmrs.github.io/openmrs-android-client-user-guide/introduction.html - User guide
• https://talk.openmrs.org/t/gsoc-2018-openmrs-android-client-3-x-project/18035?source_topic_id=19471