You can find the deployed project at moodbloomapp.com.
| Matt Klein | Janessa Maisonet | Hermione Gogou | Allison Donnelly | Amanda Lane |
|---|---|---|---|---|
 |
 |
 |
||
| Team Lead | UX Designer | UX Designer | Web Developer | Web Developer |
 |
|
|
|
|
| Brandon Pampuch | Daisy Mesa | Jeffrey Whitaker | Jonathan Taylor | Samir Lilienfeld |
|---|---|---|---|---|
 |
 |
 |
 |
 |
| Web Developer | Web Developer | Web Developer | Web Developer | Web Developer |
| |
|
|
|
|
People seeking therapy don't have a single source of truth for tracking their moods or for sharing it with their mental health provider. Due to the limitations that come with HIPAA as well as limited time for mental health providers to change their work flow, MoodBloom provides a central location for users who want to improve their overall quality of life through mood.
Users can use MoodBloom to track their mood implementing EMA strategies for their own mindfulness or to share with their mental health provider.
- Progressive Web App
- Mood tracking system
- Daily tasks to keep you on track
- Data visualizations (graphs, calendar, PDFs)
- Export data in a PDF file
- Using a JavaScript library like React gave us a lot of flexibililty to incorpororate other packages for data visualization and gamification.
- We were able to create a Progressive Web App to avoid the environment issues that come with a native mobile app making the app more accessible to those even in areas with slower internet speeds or even those who are offline.
- We wanted our application build to be quick and scalable so we could focus on the features our users need.
- We implemented Context API with Apollo-Boost to handle our state and calls to the database.
Front-end deployed to Netlify
Back end built using:
- We chose Node.js due to it's flexibility and quick set up.
- We decided to use GraphQL to query our database because it made setting up complex data shapes simpler.
- We implemented MongoDB with mongoose so we could switch our collections easily without having to alter tables or reset our database with each new version release.
Everyone likes an easy sign up process. We chose to go with Passport.js because it allowed users to use their Google login to sign up in seconds and it was a lot easier for the dev team to set up and debug. We started out using Auth0 but quickly found that it wasn't meeting our needs.
This is a library that allows you to write your GraphQL queries directly in your code just like you would in the Graphiql playground. It's like Axios but made for GraphQL.
Apollo-boost limits your global state management options and we found that Context API worked best with our tech stack.
Our UX team went with Ant Design components in our UX file so we challenged ourselves to learn the design system.
In order for the app to function correctly, the user must set up their own environment variables. There should be a .env file containing the following:
* REACT_APP_OPEN_WEATHER_API_KEY - this is your Open Weather API key, which can be generated at https://openweathermap.org/api.
* REACT_APP_CLOUDINARY_KEY - Cloudinary upload preset key
Front-end: React Testing Library with Jest
Back-end: Jest with Supertest
Fork & clone both the front-end and back-end, run yarn and then yarn start on the front-end and yarn server on the back-end.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct. Please follow it in all your interactions with the project.
If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
- Check first to see if your issue has already been reported.
- Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
- Create a live example of the problem.
- Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.
Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
- Ensure that your code conforms to our existing code conventions and test coverage.
- Include the relevant issue number, if applicable.
- You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from this good-Contributing.md-template.
See Backend Documentation for details on the backend of our project.