Reach4Help

Unifying help around the world, connecting the quarantined who need basic necessities to those who can provide it for them.
Shayan Chowdhury, Sam Lanning, Alex V, Pranav Wagh, Joseph Ashwin Kottapurath
Description
People who are at high risk from COVID-19 or are quarantined are unable to leave their houses and obtain necessities like food and medical supplies without putting themselves or others at risk. We aim to facilitate support requests for these people and act as a bridge between them and reputable volunteer organizations that can help, such as government organizations, churches and local Red Cross establishments. These organizations are all reputable and conduct the appropriate background checks on their volunteers to ensure that no foul play happens. After all, we’re trying to create a safe and familiar environment that people can count on.
We’ve reached out to a few organizations for partnerships and one of them, Vizinho Amigo, expressed concerns about coordinating their volunteer workforce to aid those in need. Going forward as we expand, we aim to create a solution to not only enable those in need to receive help, but also to enable our partners to help more efficiently by mobilizing their volunteers with the help of our own tracking and ticketing system.
Please see the Main Document for more information.
Meet the Team
Project Management
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Pedro Filipe | @puzzledbytheweb | Core Lead | UTC+0 (+1) |
@Shayan Chowdhury | @schowdhury8 | Core Lead | UTC+6 (no DST) |
@Sam Lanning | @s0 | Documentation & Product Lead | UTC+0 (+1) |
@Telmo Dias | @telmodias | Documentation Lead | UTC+1 (+2) |
@Cinthya Jauregui | @cinthyaejh | Translation Lead | UTC-8 (-7) |
Infrastructure
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Katherine Rodriguez | @edmkitty | Lead | UTC-5 (-4) |
@Jon Carlos | @webmonger | UTC+0 (+1) | |
You? |
Backend
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Wilson Rodrigues | @wr46 | Lead | UTC+0 (+1) |
@Jon Carlos | @webmonger | UTC+0 (+1) | |
@Micael Rodrigues | @micaelr95 | UTC+0 (+1) | |
You? |
Frontend
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@David Alecrim | @comoser | Lead | UTC+0 (+1) |
@Micael Rodrigues | @micaelr95 | UTC+0 (+1) | |
@Rúben Gonçalves | @rbgoncalves | UTC+0 (+1) | |
@João Marques | @jpmarques66 | UTC+0 (+1) | |
@Rafael Sanches Ferreira | @Rafaelferreiratvd | UTC+0 (+1) | |
@Luís Oliveira | @luisFilipePT | UTC+0 (+1) | |
You? |
UX / Design
Slack Channel: #project-neighbourhood-assistance-ux-design
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Telmo Dias | @telmodias | UX Lead | UTC+1 (+2) |
@Cinthya Jauregui | @cinthyaejh | UI Lead | UTC-8 (-7) |
@Sam Lanning | @s0 | UTC+0 (+1) | |
You? |
User Testing / QA
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Dan Benamy | @dbenamy | Lead | UTC+4 (+5) |
You? |
Marketing / PR
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Miranda | Lead | UTC+0 (+1) | |
You? |
Application Security
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Mathieu Deous | @mdeous | Lead | UTC+1 (+2) |
@Miguel Fernandes | @mdmfernandes | UTC+0 (+1) | |
You? |
Map Project
Slack | GitHub Handle | Role | Timezone (DST) |
---|---|---|---|
@Dan Sabin | @sabind | Lead | UTC-8 (-7) |
You? |
This project is part of Helpful Engineering, a collection of "Helpful Engineers" who have congregated to help in the COVID-19 Coronavirus Pandemic.
This project is currently still in the proposal stage, but we're already marching ahead to get a head-start, in anticipation of it advancing beyond that stage.
Tech Stack
- Frontend: React/Gatsby (PWA)
- Backend APIs: Node.js (Strapi)
- DB: MongoDB
- CI/CD: Temporarily Heroku, will be moving to Azure
Get Involved
We're still in the very early stages, and yet to complete fleshing out the various project teams and leaders. But you are welcome join the conversation and express your interest in volunteering.
- Main Document: Learn more about our mission in our Main Document.
- Slack Channel: Join our Slack - reach4help.slack.com
- GitHub Project Board: Watch our progress through our tasks and milestones on our Main Project Board.
- Volunteer Sign-Up Form: Apply to become a member of our team by filling out this form!
Project Status
Repositories
All of our main repositories are hosted under the reach4help org, including:
Infrastructure and Deployment
We will be using heroku in the early stages of the project to deploy to a test domain. https://dashboard.heroku.com/apps/reach4help
UX & Design
We have an initial Mural UX mockup for the app that you can see here.
We're actively working on the UX / Workflow here.
And some initial Figma design mockups here!
MVP Workflow:
Volunteer
- Users can register to volunteer using Facebook ID login (restricting users with accounts created for less than 6 months). If the user doesn't have Facebook we can provide and email for them to contact but we shouldn't waste too much time in this phase;
- User will be notified of cases near to them (eventually in real-time push notifications); they can then pick them up or not do anything; we might filter the notification messages inside of the app to only show the cases that are still open at the moment the user opens the notifications menu;
- Once the user understands the request is met, they can close the case as solved.
- User should agree to have their name and rating be public (+rep).
Person In Need (PIN)
- User can register via phone number. We confirm with SMS/verification code;
- Onboarding process to register person, address, etc. If registration is for another person it might be a good idea to add a phone number to call in case of request assignment. For example to enable an elder person to receive a phone call by the volunteer assigned to its request;
- Create request;
- Be notified when request is assigned;
- Extra step asking if PIN wants to accept volunteer
- Receive their requested goods/care. Volunteer should have the power to change the request status to solved, but PIN has final say.
- If the PIN has access to the app (e.g. is not elderly/owns a smartphone) they can confirm the status change.
- If the PIN cannot do the status confirmation via app, follow up to verify if the request was fulfilled.