I’m wondering the viability of forking off of the capture app, and adding script that would save the requests it takes to load Capture app onto a local device, and thereby could potentially allow for a single load of Cpature to permit someone to access the Capture app (even without internet, so long as they have loaded it prior).
Obvious caveats that I could think of is that in order to sync data there would need to be an authentication involved, and that the offline app wouldn’t even attempt to search for existing data. There would also have to be some ability to “sync to device” the data that you are going to be syncing, once you are able to get online, and a “sync to DHIS2” for when you are actually online and able to do so.
Is this crazy to assume that building this from the orignal Capture App isn’t crazy?
It would be interesting to look more into this! I’m wondering if you mean the web Capture app or the android Capture app? Thanks!
I know the android Capture app has syncing options, are there issues with that or do you actually mean the web Capture app? It doesn’t already support offline use, right? If so I think the idea sounds fantastic.
Thanks @Gassim for sure the Android is customized for an offline/online settings already. I’m talking specifically about the web Capture App. The Capture App does have some limited functionality already—but there are definite limitations and lack of stable success, particularly if you’re looking to navigate across OrgUnits, Programs, and capture many events while offline. Or at least this has been our experience!