Project: Develop an Android mobile application to show patient friendly costs of care

Exactly, for that purpose we must have a backend, pulling the CDM data into a device is tough job, as every hospital’s link for CDM is stored deeply somewhere in their website - moreover after fetching the CDM we need to parse and process it, and as the hospitals don’t allow to fetch CDM for a particular procedure - that’s where our backend will help

See above. I just conceded – but the backend isn’t necessary for the POC but definately provide something like a table in your proposal that says:

  • What HTTP methods are acceptable
  • What data is needed
  • What data is returned

Yes, not only easier, it’s a feasible way to do

I was thinking out loud, sorry for confusing you folks!

No Problem, I have included all details about backend needed in my proposal

I haven’t looked but did you trim it down to no more than 15 pages?

In my proposal I have briefly described all the API endpoints, that the android client will have access to, does that sounds fair enough?

I would prefer a table to be honest. You should plan this ahead of time. Tables are easy to understand at a glance, we have a lot of proposals to look at.

Yes , @r0bby @muarachmann It has 18 Pages now with UI Mockups Images and shared as Google Doc I have also added ER Diagram for database

Yeah sure, I will polish my proposal for ease of understanding

Hello @r0bby @muarachmann I have added UI mock ups in my draft proposal and also have significantly improved the readability, included fine details and removed redundant informations. Please have a look at it, a feedback is much appreciated.

Neither of us are the people who will make the final determination, you realize this, right?

I believe, there are mentoring organizations and Org admin’s involved. But if my proposal has made you ask me this, I must be doing something wrong.

  • mentoring organizations = LibreHealth, etc
  • mentors = LibreHealth community members
  • Org admins = people who prepared the application and such.

Now as Org Admins, myself, @sunbiz, or @judywawira am the one to determine the number of slots we need and then mark them as accepted or not. The decision is left to mentors for the projects largely unless very obviously spam.

I have experience what bad proposals look like and what good ones look like so this is why I’m reviewing them…I’m not reviewing the content in-depth unless I see you have a low number of pages.

I understand how it works

And I see, my proposal has fallen into the bad category, I will try and educate myself upon this, will try making a better one.

It has not. The mentors just haven’t reviewed it yet – if you proposal falls into that category, I would tell you.

That’s a relief, thank you. In the meantime, I have a few questions

  • As for this project, we have to implement a backend and a client - So how much detailed information is required?
  • I have included UI mockups - Do I need to update my POC just to show, that I am capable of designing the UI in real applications too?
  • How many slots does an organization get? As it’s a paid slot, who decides or rather on what factor, which students are selected? Does it depend on the project? Or on the student’s proposal’s also?

Confidential. We request it based on the number of viable proposals we get. Knowing that number won’t provide you with any insight…we haven’t even done the request yet, but even when we do, it’s not going to help you discern if you’re being selected or not.

Ideally.

Enough that we know you’re competent enough to do the project. It’s a balancing act.

No, I meant, if it’s a priority project then that makes a difference.

Yes, I understand. Thanks :slight_smile:

Will do

If we don’t have viable candidates, we won’t run the project this year. We’re trying to not repeat what happened last year where all students failed. Hoping that doesn’t happen. We want to ensure we filter out people who talk a good game, but won’t deliver. This is why I’m refusing to answer questions answered by doing basic research.