FamiLead

Sign In Screen
Main Screen

Inspiration

We noticed that household management (dividing up responsibilities and chores, sending grocery lists, communication, and upcoming events, finding places to go, etc.) is divided across several platforms, resulting in information being forgotten, lost, and having to be resent. Our platform combines all aspects of family life so that in this digital age, families are brought together instead of separated across devices. You can think of it as a workflow management platform for the home.

What we learned

Throughout this hackathon experience, we were able to learn about cool tools and technologies to help support this application with all of its features. We learned how to effectively pitch an idea, by incorporating personal experiences to explain our thinking. On the technical side, we learned how to incorporate Twilio, Firebase, and Google APIs into our React project. Finally, the execution of the web app was a super cool learning process. We learned how to incorporate a Google Maps API into our web app to allow for user interaction.

How We Built It

FamiLead was built upon React as the frontend and Node.js as the backend, with Firebase serving as the database system and the method of hosting the application. TailwindCSS was used to style the application, allowing for smooth, easy-to-use user experience. The embedded map was created using the Google Maps API, and the todo list functionality was built using Firestore Cloud functions.

Challenges

We have faced many problems along our journey. From small things like forgetting to install npm to reinstalling react and firebase and redoing the entire project. Our biggest challenge came up when we were using GitHub to separate the project into different branches and merge partial solutions together. The data had many conflicts and we were forced to start from scratch and take a different path to the problem at hand. This consumed many hours of our work time as we had been working on a solution until mid-afternoon before restarting. Luckily, we learned a great amount about the methods we had to take to create this app, so we were able to take this alternative path much quicker and almost finished by the end of the day.