## Inspiration

With the recent Corona Virus outbreak, we noticed a major issue in charitable donations of equipment/supplies ending up in the wrong hands or are lost in transit. How can donors know their support is really reaching those in need? At the same time, those in need would benefit from a way of customizing what they require, almost like a purchasing experience.

With these two needs in mind, we created Promise. A charity donation platform to ensure the right aid is provided to the right place.

## What it does

Promise has two components. First, a donation request view to submitting aid requests and confirm aids was received. Second, a donor world map view of where donation requests are coming from.

The request view allows aid workers, doctors, and responders to specificity the quantity/type of aid required (for our demo we've chosen quantity of syringes, medicine, and face masks as examples) after verifying their identity by taking a picture with their government IDs. We verify identities through Microsoft Azure's face verification service. Once a request is submitted, it and all previous requests will be visible in the donor world view.

The donor world view provides a Google Map overlay for potential donors to look at all current donation requests as pins. Donors can select these pins, see their details and make the choice to make a donation. Upon donating, donors are presented with a QR code that would be applied to the aid's packaging.

Once the aid has been received by the requesting individual(s), they would scan the QR code, confirm it has been received or notify the donor there's been an issue with the item/loss of items. The comments of the recipient are visible to the donor on the same pin.

## How we built it

Frontend: React  
Backend: Flask, Node  
DB: MySQL, Firebase Realtime DB  
Hosting: Firebase, Oracle Cloud  
Storage: Firebase  
API: Google Maps, Azure Face Detection, Azure Face Verification  
Design: Figma, Sketch

## Challenges we ran into

Some of the APIs we used had outdated documentation.
Finding a good of ensuring information flow (the correct request was referred to each time) for both the donor and recipient.

## Accomplishments that we're proud of

We utilized a good number of new technologies and created a solid project in the end which we believe has great potential for good.

We've built a platform that is design-led, and that we believe works well in practice, for both end-users and the overall experience.

## What we learned

Utilizing React states in a way that benefits a multi-page web app
Building facial recognition authentication with MS Azure

## What's next for Promise

Improve detail of information provided by a recipient on QR scan. Give donors a statistical view of how much aid is being received so both donors and recipients can better action going forward.

Add location-based package tracking similar to Amazon/Arrival by Shopify for transparency
## Inspiration

Covid-19 has turned every aspect of the world upside down. Unwanted things happen, situation been changed. Lack of communication and economic crisis cannot be prevented. Thus, we develop an application that can help people to survive during this pandemic situation by providing them **a shift-taker job platform which creates a win-win solution for both parties.**

## What it does

This application offers the ability to connect companies/manager that need employees to cover a shift for their absence employee in certain period of time without any contract. As a result, they will be able to cover their needs to survive in this pandemic. Despite its main goal, this app can generally be use to help people to **gain income anytime, anywhere, and with anyone.** They can adjust their time, their needs, and their ability to get a job with job-dash.

## How we built it

For the design, Figma is the application that we use to design all the layout and give a smooth transitions between frames. While working on the UI, developers started to code the function to make the application work.

The front end was made using react, we used react bootstrap and some custom styling to make the pages according to the UI. State management was done using Context API to keep it simple. We used node.js on the backend for easy context switching between Frontend and backend. Used express and SQLite database for development. Authentication was done using JWT allowing use to not store session cookies.

## Challenges we ran into

In the terms of UI/UX, dealing with the user information ethics have been a challenge for us and also providing complete details for both party. On the developer side, using bootstrap components ended up slowing us down more as our design was custom requiring us to override most of the styles. Would have been better to use tailwind as it would’ve given us more flexibility while also cutting down time vs using css from scratch.Due to the online nature of the hackathon, some tasks took longer.

## Accomplishments that we're proud of

Some of use picked up new technology logins while working on it and also creating a smooth UI/UX on Figma, including every features have satisfied ourselves.
Here's the link to the Figma prototype - User point of view: [link](https://www.figma.com/proto/HwXODL4sk3siWThYjw0i4k/NwHacks?node-id=68%3A3872&scaling=min-zoom)

Here's the link to the Figma prototype - Company/Business point of view: [link](https://www.figma.com/proto/HwXODL4sk3siWThYjw0i4k/NwHacks?node-id=107%3A10&scaling=min-zoom)

## What we learned

We learned that we should narrow down the scope more for future Hackathon so it would be easier and more focus to one unique feature of the app.

## What's next for Job-Dash

In terms of UI/UX, we would love to make some more improvement in the layout to better serve its purpose to help people find an additional income in job dash effectively. While on the developer side, we would like to continue developing the features. We spent a long time thinking about different features that will be helpful to people but due to the short nature of the hackathon implementation was only a small part as we underestimated the time that it will take. On the brightside we have the design ready, and exciting features to work on.
**Previously named NeatBeat**

## Inspiration

We wanted to make it easier to understand your pressure, so you **really** are not pressured about what your heart deserves.

## What it does

**Track and chart blood pressure readings** 📈❤️

* Input your systolic and diastolic to be stored on the cloud
* See and compare your current and past blood pressure readings

**Doctor and Patient system** 🩺

* Create doctor and patient accounts
* Doctors will be able to see all their patients and their associated blood pressure readings
* Doctors are able to make suggestions based on their patient readings
* Patients can see suggestions that their doctor makes

## How we built it

Using Django web framework, backend with Python and front development with HTML, Bootstrap and chart.js for charting.

## Challenges we ran into

* Too many front end issues to count 😞

## Accomplishments that we're proud of

* Being able to come together to collaborate and complete a project solely over the internet.
* Successfully splitting the projects into parts and integrating them together for a functioning product

## What we learned

* Hacking under a monumental school workload and a global pandemic

## What's next for NeatBeat

* Mobile-friendly interface