Emoup App

EmoUp is the one-stop solution for all things positive. The problem with the existing solution is that they depend on the manual inputs from the user to analyze the mood, whereas we use face recognition and emotion detection with the help of neural networks. With current circumstances affecting the mental health of people, especially teens and young adults, speeches, reports, and more. It is mostly presented before an audience.

Install App Here

Objective

EmoUp’s objective is to:

• Improve mental health.
• Intelligently get the person's emotion
• Provide an emotion rebalancing centre.
• Use various therapy to get a cheerful mood back.
• Also, a whole new relaxing world created using echo-AR.

EmoUp has now come to your smartphone for help.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Architecture

Name	Description	Language	Source code
Frontend	Mobile Application	Dart	https://github.com/EmoUP/EmoUP-Flutter
Backend	Fast API	Python	https://github.com/EmoUP/EmoUP-API

Requirements

• Any operating system (i.e. Linux, Windows, MacOS X)
• A little knowledge of Flutter and Python. Don't worry if you are new to it, you just need knack to learn.
• Any IDE with Flutter installed (i.e. VSCode, Android Studio, etc)

Development Setup

Frontend

• Install Flutter.
• Add Android Studio and setup android device or android emulator
• Now, run the flutter doctor

To start App

• git clone https://github.com/EmoUP/EmoUP-App.git
• cd EmoUP-App
• flutter pub get
• flutter run

Backend

• Python >= 3.7
• Requirements listed on requirements.txt
• Running MongoDB server

Contribution Guidelines

Please raise a feature request or issue before sending PR for the same.

Follow the below guidelines for proper coding practices:

• Always create a new branch for your changes and make PR from it ONLY.
• Write neat code with proper comments.
• Follow PEP8 coding style.
• Write descriptive commit messages. Please read this for more information.
• Write detailed PR messages and include fixes #ISSUE_NUMBER it if closes an issue, otherwise use concerns #ISSUE_NUMBER to tag the related issues. Please refer here for more PR guidelines.
• It is recommended to have a single commit for a task.
• Use DRY principles to create maintainable code.

Authors

• Abhi Jain
• Ajinkya Dandvate
• Ajinkya Taranekar
• Krati Jain