Primary mentor | |
Backup mentor | N/A |
Assigned to | N/A |
...
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.
There The 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. Also, the 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.
Finally, seeing the number of components in the web app, the Android app should integrate more of them 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.
...
- The features added or modified must be documented in the hosted at OpenMRS client user guide with the github repository here.
Resources
- OpenMRS Android Client Project 2.9.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