test
testing
Updates
Leave feedback in the comments!
Purpose
The major purpose of our project is to create a dynamic tool that allows college students to take care of their mental health on busy days with short but meaningful “happy thoughts”. With a simple process to keep the daily mood and gratitude logs on our app, students become aware of their wellbeing by taking action and gratitude for positive things/objects/events around them.
The app also aims to encourage practicing gratitude and mindfulness practice for those who are suffering from anxiety and depression. By writing and keeping the gratitude logs through our app, users will improve their mental health and change their perception of life. The app intends to teach you how to be more thankful every day and treat yourself through the power of gratefulness.
How does the application work
This application works on the web and it is adapted to mobile by running npm as indicated in the instructions in the Git repo.
How was the application developed
This application was developed using React.js to build the user interfaces in a framework which was easy to follow by the involved developers. REsponsive web design was implemented to allow the application content to respond to the different screen and window sizes. During the application development, prototyping tools such as CodeSandBox were used to test algorithms online before directly implementing them to Visual Studio Editor. This allowed less-experienced developers to rapidly test their algorithms and feel free to play with modifications without breaking compiled algorithms. Other libraries such as Bootstrap and Material Icons from Google were used to speed up the styling and design. Developers contribute to the public repositories named “Gratreat” and “Gratreat-Api” of the GIT-MHAH-GratTreat Organization.
How to use the application
User will first have to sign in to the web app in order to access the tools Once the user has logged in they are given the options of creating a new entry, looking through their records or checking how many points they have to get a treat from a vendor When they pick a mood they will be redirected to a new page where they can select prompts or skip the prompts selection If they pick the prompts then the user would go to a section in the site where they use that prompt as a topic of their journal entry Each prompt has a save button so when the user has completed a specific log they can click on the that button in order for it to be in their records section If they chose to skip the prompts then the user would go to a blank journal entry section. After they write something down they would click on the submit button which will save their entry in the records section When user click on the submit button they will shown a pop up which show them how many points they earned with their entry as well as give them the options to either go the their records page or rewards Every time the user saves a log they will be given points which they can use for getting treats from vendors Users can access the treats page by clicking on the link on the footer nav They can select a treat using points that they earned
Difficulties & Challenges faced during the design and/or development process.
Several challenges were faced in various aspects of the application development. For this, difficulties and challenges have been divided into sections. Challenges faced during:
Development:
- Lack of experience in building functions in React to render essential elements of the application. For instance, the code to build the final calendar (page number 6 in wireframe) required more programming experience/skills from the developers than the team thought. Swapping components was another feature that was impossible to implement for the same reason and was considered for page number 5 in wireframe.
- The documentation to install dependencies using npm could be complicated when developers look for a specific open-resource up to date.
- The addition of icons was difficult because the documentation was hard to find and the icons names were mixed up. We also found the names were repeating for more than one icon and the class name would not work to call the desired icon.
Communication: 1. The continuous communication between team members was affected due to the limited time that Google Meet or Zoom provides. Slack was useful for continuous texting, however it does not allow free video chats.
General organization: No major challenges were faced with the general organization of the project. Each group member had a role to play and were able to deliver items in a timely manner.
Time Management: Some components were not completed due to the time limit. Including features such as the tracker page.
Go-to-Market (How will the application be available to the public, and is it scalable?)
The project is scalable since other features are needed to be added such as user authentication which will help keep track users logs and also gives indications of how many people are continuously using the app. Second, we can make the website available as a mobile app on the app store which would make the website more convenient to use. Third, adding a swipe feature to the app
Log in or sign up for Devpost to join the conversation.
Log in or sign up for Devpost to join the conversation.