Hi @Omkar-Jori please follow the thread and all communications must be public. Post your work here
thank you for reply, i kindly work on prerequisite as soon as possible.
Everything is public. So I hope you didn’t private message any of them.
@muarachmann @r0bby please give feedback on my draft proposal that I have shared.
You should also be including @sunbiz and @judywawira – they’re the ones you need to impress.
also did you do the task prerequisite?
Hi @muarachmann @r0bby @sunbiz. I have completed my POC for the backend application. I had already submitted my POC for the main application earlier. Please check it out https://github.com/AdarshPanigrahi/librehealth-admin and share your feedback .
1 Like
- Why didn’t you use packages to organize your activities? That’s why they’re there.
- Please have
Activityat the end of all Activity classes. - Each of your android app component types should live in their own package, adapters, activities, etc.
Folks,
If you submit your proposal and do not do the Task prerequisite, we will not consider your proposal.
It also reflects very poorly on you that you have poor attention to detail. Don’t do this.
@r0bby Sorry for that. I will keep that in mind next time .
But other than that is it fine to use another android application as a backend or it is mandatory to useweb application for backend services ?
I didn’t run it – I’m looking at it from a class naming POV – I’m a stickler for conventions and kinda OCD how I organize Android app classes into a coherent package structure.
Is there a reason to put this into a database? Why not put it into a git repo on Gitlab after scraping (the scraper could use a CI) and the client only checks by doing a git pull to know if there are any changes.
This is going to be network intensive for the client, and I suggest against doing this.
Using firebase is an interesting idea because then the client doesn’t have to even look to “pull” for changes. Firebase allows for push, and so when the database is updated, the client can get the update.
This was me suggesting and then quickly realizing it’s a bad idea.
Most of the messages quoted above are more or less a byproduct of the discussion and me coming to the realization that scraping on the device was a bad idea.
The Firebase Realtime Database Feature? We might not need it. The change of CDM’s are not so abrupt to use this.
According to my suggested idea, the client (android app) never looks for changes, it just queries the backend, and it’s backend’s responsibility to provide the updated CDM details.
As far as the backend is concerned, then I have an interesting idea to update the database on our backend (I will put that in my proposal) - also why use a 3rd party service (Firebase) while we are developing our own dedicated backend.
I can use github repo to store CDM. I can then download nearby Hospital’s CDM of user from app .User can then search in downloaded CDM.
I don’t need database then.
Please suggest .
I will add this idea in my proposal and share with you soon.
I would have appreciated the idea, but then again what’s the use of our backend? It’s dedicated for this purpose only, right? How will you put the CDM in the GitHub repo? you must be using a backend, then why not make the backend do everything?
@sunbiz This is the reason I’m trying to avoid using a 3rd party service. Correct me if I am wrong anywhere.
Let’s suppose there are 15 hospitals within a radius of 10 km, then fetching CDM for 15 hospitals and then searching through hundreds of procedures among them, is both unrealistic and network intensive. I guess better we use our backend to do the filtering and searching, and let the android app just display.
That’s more reason not to add a GET request from client very often. In REST you can achieve this through ETags, but again there are simpler alternatives like git. You can get all the CDMs or only the updated CDMs into the app through Firebase, or only changed files through git
IMO, an important part of a good backend (for this use-case) is maintaining changeset. You can calculate historical price changes, seasonal changes, demand-supply fluctuations that a traditional database design won’t be able to handle automatically. You’ll need to design for that.
The backend crawler like I said could run on a CI service (or one of our lh servers) that crawls the links every few hours and puts the CDM files on git. I don’t expect the CDMs to be retrieved based on location. Those should be on the device and updated as and when the backend updates or the app restarts and finds a changeset.
@mr.paul App will download nearby hospital’s CDM only once from github & then user can search in downloaded CDM. We only need to search in dowloaded CDM.
Please correct if I am wrong. @r0bby @sunbiz @muarachmann
1 Like
I understand, developing a backend is then not necessary, a backend crawler can be used to put the CDM files on Firebase - we can use necessary queries to fetch for particular hospitals or procedures, and for maintaining the changeset - we can use git. Somehow we need to see how to manage between git and firebase.
@sunbiz This idea is pretty interesting, I will explore it.
Hi mentors, The project sounds interesting. I would like to contribute to this project. Now what to do next and how to prepare a good proposal for this project? I am eagerly waiting for your reply. Thank you.
I have a question 
Why are we downloading the CDM’s via Github? What’s the point? Download nearby hospital’s CDM from their websites directly, then search in that.
I understand git is introduced for maintaining changeset - but we aren’t using that here.