Inspiration
In brainstorming for a hackathon project that would help to empower women, we asked others if there was an application that could benefit them as a woman. One of our friends mentioned that it would be useful to create an app that would help to view nutrients that are recommended at different phases of the menstrual cycle to balance hormonal changes.
What it does
Our app uses menstrual cycle information, provided by the user, to give personalized food suggestions to fulfill typical nutrition needs throughout the phases of the cycle (menstrual, follicular, ovulation, luteal). It takes in cycle flow, symptoms, and mood information from the user, and displays phase of the cycle and lists of food recommendations and where to get these foods.
How we built it
Our web application is built with the React framework and using the Material UI library for some of the features. We created different React components for the different parts of the application. We worked on using Flask with Python for the backend side of our project.
Challenges we ran into
With different members working on separate parts of the project, we ran into some others while merging our code as well as using different resources that conflicted with each other. We were able to fix our merge conflicts and figured out that when one member used the react-bootstrap framework, it had modified the layout of other parts of the site as well. However, we were able to overcome this by modifying that section.
Accomplishments that we're proud of
With some of our team members learning about React for the first time and working with unfamiliar resources, we're proud to have created a clean UI that includes a form to submit cycle/symptom/mood information, lists of food recommendations/places to get the food, and general information about the phase that the user is currently in. We also have a navbar at the top, that includes buttons to authenticate via Google, visit our about page, and sign out.
What we learned
In addition to learning React for some of us, we also become more familiar with using Git on the project. We dealt with merge conflicts and became better at avoiding them. With working on different parts of the project, we also practiced our communication skills in discussing next steps throughout the process and any problems that we faced.
What's next for .meal
Currently, our backend is not yet functional--our next steps would be to connect the input form to the lists, phase information, as well as the timeline displayed at the top.
Log in or sign up for Devpost to join the conversation.