Making OpenMRS Android Client easily customizable.

[saurabh (Saurabh Kumar)]

At present android client works more like a standalone software which can be used, but its really hard to customize it for any implementation.

Customizing/Wrapping of Android Client

@rishabh997 Actually you can use Reference Application as a baseline, with the ability to change some of these settings for different implementations, I am thinking of UgandaEMR as just one of those I am not an expert on Android development, is there a way I can setup a new Android project that uses the OpenMRS android client as a module, so that one can override some settings and configurations?

This thread initiated by @ssmusoke in which he indicates that refapp can be used like a baseline and implementations can build on top of it without forking the refapp.

we are still not near the flexibilty we would want but following this series of Tasks

https://issues.openmrs.org/browse/AC-812

we have tried to decouple the presenters with the repository methods which handle the app’s interaction with the servers.

@ssmusoke will it be helpful if all the code which acts as an interface between the UI, presenters and the actual servers is encapsulated as a Jitpack library so that implementations can build on top of the methods exposed via the repository classes and build customized UI without forking the android client.

To leverage the jitpack library we would just need to add it as a dependency rather than forking the whole android client making it difficult to customize as was the case in this post

Customizing/Wrapping of Android Client

I would like to hear some ideas for how implementors can customize the Android client for their own needs for example Look and Feel Tabs displayed for a patient - Allergies, Vitals, etc Registration Form Ability to specify an end-point or criteria for selecting a list of patients instead of having to search for them Manual syncing and prompts when editing patient data I am also wondering how this is done in the Android world, without forking the code, can one use the client as a library then …

Would love to hear more thoughts and suggestions on this, and more insights into how refapp actually makes itself easily extendable .

cc @ssmusoke @dkayiwa @rishabh997 @gcliff

[shivansh221b (Shivansh Goel)]

Hello there, @saurabh, I’ve been planning to implement the offline structure for various features in the Android Client (which is only for the Provider module so far as stated on the wiki page). But I am having a hard time understanding how the Provider module is working offline, if you can please guide me through it, I will be planning my approach to do this effectively.

[saurabh (Saurabh Kumar)]

does it help @shivansh221b

AC-747 Adding offline support for the provider module

I think this read would be good for you

[shivansh221b (Shivansh Goel)]

Yes it does, thank you @saurabh

[shivansh221b (Shivansh Goel)]

One more thing @saurabh sir, we can add, edit and delete patients in offline mode and as of the PR you mentioned, Provider too. and as in the PR - 729 the offline Visits are disabled and also Allergies can also be managed offline. Then what functionalities are still needed to be implemented in offline mode?

[saurabh (Saurabh Kumar)]

@shivansh221b

and as in the PR - 729 the offline Visits are disabled and also Allergies can also be managed offline. Then what functionalities are still needed to be implemented in offline mode

we want to homegenise the offline structure, its not coming all together at the moment there are some Issues with the provider offline structure which needs to be fixed and generalized across all the modules in similar way.

The Patient module still uses services for the purpose while the provider module uses much higher abstraction which is the work-Manager for this purpose.

@shivansh221b

One more thing @saurabh sir

you can drop the sir feels weird Im still a undergraduate student

[shivansh221b (Shivansh Goel)]

@saurabh

you can drop the sir feels weird Im still a undergraduate student

Sure thing

@saurabh

we want to homegenise the offline structure, its not coming all together at the moment there are some Issues with the provider offline structure which needs to be fixed and generalized across all the modules in similar way.

The Patient module still uses services for the purpose while the provider module uses much higher abstraction which is the work-Manager for this purpose.

So, does that mean that the offline structure is ready(which was implemented for the provider module) and just needs to be fixed and generalized to be used in all modules???