Google Summer of Code (GSoC) at LibreHealth

Hey Everyone, I am back with my weekly updates about my GSoC journey😀. This amazing journey is about to its end guys, but really I never forget this great experience where I learned a lot of technologies & experienced a new tech side of android development in just a few weeks. This week I had a meeting with my mentor where I discussed some of the UI-UX related stuff that can make the user experience much better. Hence I have improved the UI of the app, uploaded educational resources over dhis2, find out some very important bugs that need to be resolved in the scale-up version. Let’s discuss them one by one - Segregated Media Resources into Categories- Earlier all types of media files either it is pdf, video, xls file, doc., etc. everyone is present in the single page. Since we have more video resources and Pdfs I have made out the filter options to view resources into 4 separate sections All Media, Videos, PDFs and Other files. Related Issue: Issue #195 Related MR: MR #199 Media

  Hey Everyone, this week I have fixed the tracker app pipeline that failed last week, exported the tracker and trainer specific metadata, tested them by importing them to the play servers and a lot more. Let’s discuss this in detail.   Fixed Tracker App Gitlab Pipeline Last week when I submitted an MR that passed the pipeline and was merged by my mentor into the main repo of the tracker app but it gets failed unexpectedly. The interesting fact to note is that it ran successfully in the commit with which I had submitted but the merge commit that my mentor made to merge it which doesn’t contain any new changes, and is only having the commits that I made failed the pipeline. I didn't get any reason for it.😌 But in the end, I made it find out the cause of it and fix it😀. I think it is due to the NDK version. I suggest if you are building it locally as well please try building after installing NDK Version 21.0.6113669 Related MR: MR-15 Exported Tracker App Metadata I had exported tra

Hello Everyone, I am elated to share that project is going good and mostly all the issues are being sorted in the GitLab. This week I had tested the workflow of the apps, fixed few bugs and updated Readme and added some demonstration videos to help in the use of mhbs apps.😀

 Hello Guys. This blog is to reflect the light on the work done in 7th week of gsoc-21.😀 Tested 3–4 Issues I had go through almost all the issues of the tracker and trainer app. I had tested issues 4 issues marked with testing label and prepared their solution. I will be discussing my approaches for these issues with my mentor and fixed them in next week. Fixed mhbs Logo Issue I ssue #4 In the tracker app some of the screens have the dhis-2 logo. It is now fixed to mhbs logo. Fixed I ssue #4   Related MR : Mhbs logo fixed Updated Trainer App Readme.md Since we had added media page, offline support, app usage tracker in trainer app we want a small documentation details to be added to the readme for further reference. I had done it - Committed here ( 718f8756 ). Fixed Bug in GitLab CI There is a bug in GitLab CI code of trainer app. Gradle is building the apk correctly but it is not assembling the artifact correctly. It is my mistake what I had made earlier. I had corrected it. Committ

Hey Everyone, I am back with my weekly blog. Let’s have a look at work done in the 6th week of this amazing journey. Reimplemented and Completed App Usage Tracking System Guys actually as stated in the last blog I had completed the app usage tracking system but on discussing with the mentor We come up with a better approach and reimplemented the completed system. There are not very huge changes we just did some changes in the dhis2 storage part. Let’s have a look at how we are tracking the trainer app usage now - App usage is now stored in the user’s data store instead of the tracker program. For each page, a unique id is assigned with which the page usage is tracked in datastore and in local DB as well. There is a local DB support that will store the page usage and when the page usage exceeds the threshold limit for each usage then data will be sent to the dhis2 in the user’s datastore. When local app usage storage get synced with the dhis2 user’s data store then local DB will get res

  Hello Everyone, sorry for getting delayed in writing this blog. Last week's work is as follows:  Worked on App Usage Tracking System of Trainer App  To track the app usage I had followed these steps- Created “mHBS Trainer Usage Tracker” Tracker Program Created Tracked Entity Attributes to store [ total page visits, total time spent on a page, page visits per user, time spent on a page by per user]. Created “Page Usage Tracker” Tracked Entity with the above attributes. Created a tracker program i.e. “mHBS Trainer Usage Tracker” to track the tei created above (Page Usage Tracker). There are more than 40 pages in Trainer app. Enrolled tei for each page in “mHBS Trainer Usage Tracker” program. Now we can send data for each and every page to dhis2 in the Tracker program. 2. Created Local SQL- DB table to store app usage Users cannot remain online every time but we want the full usage of our app to track therefore we need some local storage to store app usage in offline mode and update