Mental Health & Mood Tracker App using

Frontend , chart.js , Bootstrap

A MINI PROJECT REPORT

Submitted by

RAHUL KUMAR JHA [ EC2432251010556 ]

Under the Guidance of

Dr. G. Babu

(Assistant Professor, Directorate of Online Education)

in partial fulfillment for the award of the degree of

M.C.A. - Computer Applications

DIRECTORATE OF ONLINE EDUCATION

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

KATTANKULATHUR- 603 203

JUNE – 2025

1
 DIRECTORATE OF ONLINE EDUCATION

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

KATTANKULATHUR – 603 203

BONAFIDE CERTIFICATE

This Mini Project Work Report titled “Mental Health Journal &

Mood Tracker App” by RAHUL KUMAR

JHA[ EC2432251010556 ] , who carried out the Project Work under

Programme coordinator of online education. To the best of my

knowledge, the work reported herein does not form any other internship

report or dissertation based on which a degree or award was conferred on

this or any other candidate on an earlier occasion.

2
 ACKNOWLEDGEMENT

We express our humble gratitude to Dr C. Muthamizhchelvan, Vice-

Chancellor, SRM Institute of Science and Technology, for the facilities extended
for the project work and his continued support. We extend our sincere thanks to
Director DOE, SRM Institute of Science and Technology, Prof. Dr Manoranjan

Pon Ram, for his invaluable support. SRM Institute of Science and Technology,
for her support throughout the project work. We want to convey our thanks to
Programme Coordinator Dr. G. Babu, Directorate of online Education, SRM

Institute of Science and Technology, for their inputs during the project reviews
and support. Our inexpressible respect and thanks to my guide, Dr G.Babu.,

Assistant Professor & Programme Coordinator Directorate of online Education,,

SRM Institute of Science and Technology, for providing me with an opportunity

to pursue my project under her mentorship. She provided me with the freedom
and support to explore the research topics of my interest. Her passion for solving
problems and making a difference in the world has always been inspiring. We

sincerely thank the Directorate of online Education, staff and students, SRM
Institute of Science and Technology, for their help during our project. Finally, we

would like to thank parents, family members, and friends for their unconditional

love, constant support, and encouragement.

RAHUL KUMAR JHA

3
TABLE OF CONTENT

CHAPTOR NO. TBALE PAGE NO.

1. Abstract ……………… …… ………….……………………. 5

2. Introduction …………………..……………….……………… 6

3. Analysis & Requirement ……………………………….…….. 8

4. Problem Description/Modules Description………………….. 10

5. Design ………………………………………… …………… 12

6. Implementation …………………………….………………. 21

7. Testing ……………………………………………………… 23

8. Tools ………………………………………………………. 25

9. Coding ………………………………………….………….28

9. Result ……………………………………….….…………. 34

10. Conclusion ……………………………………………….. 35

11. Reference ……………………………….………………… 35

4
 1. Abstract
The Mental Health Journal & Mood Tracker App is a digital tool designed to
help users track their emotional well-being, identify patterns in their mood, and
develop healthier coping strategies. This app combines journaling, mood
tracking, and data visualization to provide users with insights into their mental
health over time. Users can log their daily emotions, write journal entries, and
categorize moods with customizable tags. The app integrates reminders for
consistency and offers data analytics, including charts and trend analysis, to help
users recognize triggers and progress. Additionally, features such as guided
reflections, affirmations, and mindfulness exercises provide supportive
interventions. By promoting selfawareness and emotional regulation, this app
serves as a personal companion for mental wellness, fostering healthier habits
and a deeper understanding of one’s mental state.
Key Features of the Mental Health Journal & Mood Tracker App
i. User Authentication - The app incorporates robust user authentication
to ensure data privacy and security. Users can create individual
accounts, securely log in, and manage their personal financial data with
peace of mind.
ii. Mood Tracking – Log daily emotions with customizable mood
categories and intensity levels.
iii. Journal Entries – Write personal reflections, attach images, and
categorize entries for deeper insights.
iv. Data Visualization – View mood trends over time with interactive
charts and analytics.
v. Customizable Reminders – Set reminders to check in with your mood
and journal regularly.

The Mental Health Journal & Mood Tracker App leverages Next.js, a popular
React framework, to provide a fast and efficient user experience with server-side
rendering capabilities. Tailwind CSS is utilized for building a responsive and
visually appealing user interface, ensuring compatibility across a range of
devices and screen sizes. MongoDB serves as the backend database, offering
scalability, flexibility, and seamless data storage and retrieval.
In conclusion, the Mental Health Journal & Mood Tracker App offers a
comprehensive and user-friendly platform for tracking emotional well-being and
fostering self-awareness. By integrating journaling, mood tracking, data
visualization, and mindfulness tools, the app empowers users to recognize
patterns, manage emotions, and develop healthier coping strategies. Built with
Next.js, Tailwind CSS, and MongoDB, it ensures a seamless, secure, and
responsive experience, making it a valuable companion for mental wellness.

5
 2. Introduction

Mental health is a crucial aspect of overall well-being, and self-awareness plays a

key role in managing emotional health. The Mental Health Journal & Mood
Tracker App is designed to help users monitor their emotions, recognize
patterns, and develop positive mental health habits. This app provides a digital
platform for users to log their moods, write journal entries, track emotional
trends, and gain insights into their mental well-being.

By integrating features such as mood tracking, journaling, data visualization,

and reminders, the app empowers individuals to take control of their mental
health. Additionally, guided reflections, affirmations, and mindfulness exercises
support users in fostering emotional resilience.

This project focuses on designing and developing a structured, secure, and

user-friendly mental health management system. The system will incorporate
database-driven architecture, UML-based system modeling, and optimized
data flow design to ensure efficient performance and scalability. The following
sections will outline the system's detailed architecture, database design, and
implementation methodology.

To develop a Mental Health Journal & Mood Tracker App, need a combination
of front-end, back-end, database, and cloud technologies. Here’s a breakdown of
the software and tools used:

1. Front-End (User Interface & Experience)

 Frameworks/Languages:
o Flutter (Dart) – Cross-platform for iOS & Android
o React Native (JavaScript/TypeScript) – Cross-platform
o Swift (for native iOS development)
o Kotlin (for native Android development)
 UI Design:
o Figma / Adobe XD – For UI/UX prototyping
o Material UI / Tailwind CSS – If using web-based implementation

2. Back-End (Server & Logic)

 Languages & Frameworks:

o Node.js (Express.js) – Lightweight and scalable
o Django (Python) – Secure and robust for handling user data
o Firebase – Backend-as-a-Service (BaaS) for real-time sync
 Authentication & Security:
o Firebase Authentication / OAuth2
o JWT (JSON Web Token) for session security

6
 o AES/End-to-End Encryption for user journal protection

3. Database (Storing Journals & Mood Data)

 Cloud Databases:

o Firebase Firestore – Real-time NoSQL database

o PostgreSQL / MySQL – Relational database for structured data
o MongoDB – NoSQL for flexible data storage
 Local Storage (Offline Mode):
o SQLite (for offline journaling)
o Room Database (for Android local storage)

4. Cloud & Hosting (Deployment & Syncing)

 Cloud Services:
o Google Firebase (for hosting, database, and authentication)
o AWS (EC2, S3, Lambda for serverless operations)
o Azure / Google Cloud for enterprise-level scaling
 APIs & AI Integration:
o OpenAI API (for AI-generated mood insights or journaling
prompts)
o Google Cloud NLP (for sentiment analysis of journal entries)

5. Third-Party Integrations

 Health & Wearable Device Integration:

o Apple HealthKit / Google Fit – To track health metrics
o Fitbit / Garmin APIs – For stress & sleep tracking
 Push Notifications:
o Firebase Cloud Messaging (FCM)
o OneSignal

7
 3. Analysis

The Mental Health Journal & Mood Tracker App is designed to address the
growing need for self-awareness and emotional well-being through digital tools.
This analysis outlines the problem statement, objectives, functional and non-
functional requirements, and feasibility study to ensure a structured development
approach.

1. Problem Statement

Many individuals struggle to keep track of their mental health due to a lack of
structured self-monitoring tools. Traditional methods such as paper journaling
may not provide meaningful insights or analytics. This app aims to bridge this
gap by offering a secure, interactive, and AI-driven digital platform for mood
tracking and journaling.

2. Objectives

The key objectives of the system are:

 To provide a user-friendly interface for mood tracking and journaling.

 To enable trend analysis for self-awareness and emotional pattern
identification.
 To integrate reminders and guided reflections for consistent mental health
monitoring.
 To ensure data privacy and security for user entries.
 To generate insights and reports for users to understand their emotional
patterns.

3. Functional Requirements

The system must support the following:

 User authentication (signup, login, password recovery).

 Mood logging with date, time, and intensity levels.
 Journal entry creation with optional mood tagging.
 Data visualization (charts, statistics, and trends).
 Customizable reminders for mood check-ins.

8
  AI-driven insights (optional sentiment analysis).
 Exporting and sharing reports (if needed for therapy sessions).

4. Non-Functional Requirements

 Scalability – Ability to handle a growing number of users and data.

 Security – Encryption of user data and privacy controls.
 Performance – Fast data retrieval and smooth UI/UX.
 Usability – Intuitive design for users of all demographics.

5. Feasibility Study

 Technical Feasibility: The project is feasible using cross-platform

development (Flutter/React Native) and a scalable backend
(Firebase/PostgreSQL). AI-based sentiment analysis can be integrated for
advanced insights.
 Economic Feasibility: The app can be monetized via premium features
(advanced analytics, AI insights) or subscription models, making it
sustainable.
 Operational Feasibility: Users can easily integrate this into their daily
routine due to its simple UI, reminders, and mobile accessibility.

Conclusion

System Requirements

H/W System Configuration:-

 CPU type : Intel Core i5
 Clock speed : 3.0 GHz
 Ram Size : 8 GB
 Hard Disk Capacity : 1 TB
 Monitor : 19 Inch Color Monitor
 Mobile : Android

S/W System Configuration:-

 Operating System : WINDOWS 10 , Android

 Language : Java , JavaScript.
 IDE : Android Studio 2024.2.2
 Data Base : Firebase

9
  Cloud Database : Firebase
 Documentation : MS-Office

4. Problem Description

Mental health awareness has become increasingly important, yet many

individuals struggle to track their emotions, recognize triggers, and develop
effective coping strategies. Traditional methods, such as paper journals, lack
analytical insights, while existing digital solutions may not provide personalized
tracking and visualization. This gap highlights the need for a userfriendly and
data-driven tool that enables individuals to monitor their mental well-being,
identify mood patterns, and engage in reflective practices. The Mental Health
Journal & Mood Tracker App addresses this need by integrating journaling,
mood tracking, and data visualization, offering users a structured way to enhance
self-awareness and emotional regulation.

Modules Description

1. User Authentication

• Secure login and registration system to protect user data.

• Password encryption and authentication for privacy.
• Account management for personalized user experiences.

2. Mood Tracking

• Allows users to log daily emotions with customizable mood categories.

Users can set intensity levels for a more detailed emotional assessment.
Tag-based categorization for easy filtering and pattern recognition.

3. Journal Entries

• Enables users to write daily reflections and attach images.

• Categorization and search functionalities for easy retrieval. Promotes
mindfulness and self-expression.

4. Data Visualization & Analytics

• Interactive charts displaying mood trends over time.

• Identifies recurring patterns and triggers based on past entries.

10
 • Generates insights to help users make informed decisions for mental well-
being.

5. Customizable Reminders

• Users can set reminders for journaling and mood tracking.

• Push notifications to encourage consistency in mental health monitoring.
Adjustable settings for personalized check-in schedules.

6. Mindfulness & Supportive Feature

• Guided reflections and prompts to encourage deeper self-exploration.

• Positive affirmations and mindfulness exercises for emotional well-being.
Resources and self-care tips to support mental health.

By integrating these modules, the app provides a holistic approach to mental

wellness, helping users gain insights into their emotional patterns and develop

healthier coping mechanisms.

11
 5. Design

UML DIAGRAMS

UML stands for Unified Modeling Language. UML is a standardized general-

purpose modeling language in the field of object-oriented software engineering.

The standard is managed, and was created by, the Object Management Group.

The goal is for UML to become a common language for creating models of

object oriented computer software. In its current form UML is comprised of two

major components: a Meta-model and a notation. In the future, some form of

method or process may also be added to; or associated with, UML. The Unified

Modeling Language is a standard language for specifying, Visualization,

Constructing and documenting the artifacts of software system, as well as for

business modeling and other non-software systems. The UML represents a

collection of best engineering practices that have proven successful in the

modeling of large and complex systems. The UML is a very important part of

developing objects oriented software and the software development process. The

UML uses mostly graphical notations to express the design of software projects.

GOALS:

12
The Primary goals in the design of the UML are as follows:
1. Provide users a ready-to-use, expressive visual modeling Language so that
they can develop and exchange meaningful models.
2. Provide extendibility and specialization mechanisms to extend the core
concepts.
3. Be independent of particular programming languages and development
process.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of OO tools market.
6. Support higher level development concepts such as collaborations,
frameworks, patterns and components.
7. Integrate best practices.

1. Use Case Diagram

A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose
is to present a graphical overview of the functionality provided by a system in
terms of actors, their goals (represented as use cases), and any dependencies
between those use cases. The main purpose of a use case diagram is to show
what system functions are performed for which actor. Roles of the actors in the
system can be depicted.
This diagram shows user interactions such as login/register, adding mood entries,
journaling, accessing analytics, and logging out.

13
2. Class Diagram

In software engineering, a class diagram in the Unified Modeling Language

(UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or methods),
and the relationships among the classes. It explains which class contains
information.
This diagram displays the system’s structure including classes like User, Mood
Entry, Journal Entry, and their relationships.

14
3. Sequence Diagram

A sequence diagram in Unified Modeling Language (UML) is a kind of

interaction diagram that shows how processes operate with one another and in
what order. It is a construct of a Message Sequence Chart. Sequence diagrams
are sometimes called event diagrams, event scenarios, and timing diagrams.
This sequence diagram outlines the interactions between the user and system
over time for key operations like logging in and tracking mood.

15
4. Collaboration Diagram
In collaboration diagram the method call sequence is indicated by some
numbering technique as shown below. The number indicates how the methods
are called one after another. We have taken the same order management system
to describe the collaboration diagram. The method calls
are similar to that of a sequence diagram. But the difference is that the sequence
diagram does not describe the object organization where as the collaboration
diagram shows the object organization.
This diagram displays the communication among objects using numbered
method calls starting from 1.

16
 1 : Resister
2 : Login
3 : WriteJournalEntry()
4 : trackMood()
\
User System
5 : viewInsights()
6 : setReminder()
7:editJounalEntry()
8 : logout(0

5. Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise

activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the
business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control.
This activity diagram visualizes the workflow from user login to mood tracking
and viewing analytics.

17
18
6. Component Diagram

Component diagrams are used to describe the physical artifacts of a system. This
artifact includes files, executable, libraries etc. So the purpose of this diagram is
different, Component diagrams are used during the implementation phase of an
application. But it is prepared well in advance to visualize the implementation
details. Initially the system is designed using different UML diagrams and then
when the artifacts are ready component diagrams are used to get an idea of the
implementation.
This diagram presents the physical components like the database, API server,
mobile app interface, and how they interact.

19
20
6. Implementation - Mental Health Journal & Mood Tracker App

Technology Stack

 Frontend: Flutter (for cross-platform mobile development)

 Backend: Node.js with Express (for RESTful API development)
 Database: Firebase Realtime Database / Firestore (or alternatively,
PostgreSQL)
 Authentication: Firebase Authentication or OAuth 2.0
 Cloud Services: Firebase Cloud Functions, Google Cloud / AWS
 Analytics & Sentiment Analysis (optional): TensorFlow Lite or third-party
NLP API
 Notifications: Firebase Cloud Messaging (FCM)

Frontend Implementation

 UI/UX Design: Developed using Flutter widgets with Material Design and
Cupertino (for iOS-like styling).
 Key Screens: Login/Signup, Home Dashboard, Mood Tracking, Journal
Entry, Analytics & Reports, Reminder Setup, Settings.
 State Management: Using Provider or Riverpod for app-wide state
management.

Backend Implementation

 RESTful APIs: Developed using Node.js with Express framework.

 Key API Endpoints:
 - POST /login – User login
 - POST /register – User registration
 - POST /mood – Add mood entry
 - GET /moods – Retrieve mood history
 - POST /journal – Add journal entry
 - GET /journal – Retrieve journal entries
 - GET /analytics – Generate mood trend report

21
 - POST /reminder – Set new reminder

Database Implementation

 Firebase Schema:
users/
userId/
profile: { name, email, preferences }
moods/
moodId: { mood, intensity, timestamp, note }
journals/
journalId: { content, moodTag, sentiment, timestamp }
reminders/
reminderId: { time, frequency }
 SQL Schema: Tables include Users, MoodEntries, JournalEntries, Reminders,
Analytics.

Security Implementation

 Authentication: Firebase Authentication with token-based verification.

 Data Encryption: HTTPS and hashed sensitive data.
 Access Control: Role-based access for users and admins.

Notifications & Reminders

 Implemented using Firebase Cloud Messaging (FCM).

 Scheduled local notifications for journaling and mood check-ins.

Analytics & AI Insights (Optional Module)

 Sentiment analysis using pre-trained NLP models or APIs (e.g., Google

Cloud NLP, IBM Watson).
 Charts and graphs using fl_chart or Chart.js.

22
 Mood pattern analysis over time using line and pie charts.

Testing

 Unit Testing: Flutter's test package and Jest for backend.

 Integration Testing: End-to-end functional testing.
 User Testing: Feedback from beta users for UI/UX improvement.

Conclusion

 Focus on modularity, scalability, and user-centric design.

 Cloud services and secure data ensure a reliable and responsive app.
 Provides mood tracking, journaling, and AI insights for better mental
wellness.

7. SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, subassemblies, assemblies and/or
a finished product It is the process of exercising software with the intent of
ensuring that the Software system meets its requirements and user expectations
and does not fail in an unacceptable manner. There are various types of test. Each
test type addresses a specific testing requirement.

TYPES OF TESTING

UNIT TESTING:
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is
the testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing,
that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business
process performs accurately to the documented specifications and contains
clearly defined inputs and expected results.

23
INTEGRATION TESTING
Integration tests are designed to test integrated software components to
determine if they actually run as one program. Testing is event driven and is
more concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as
shown by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components
FUNCTIONAL TEST:-
Functional tests provide systematic demonstrations that functions tested are
available as specified by the business and technical requirements, system
documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields,

predefined processes, and successive processes must be considered for testing.

Before functional testing is complete, additional tests are identified and the
effective value of current tests is determined.

SYSTEM TEST
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-
driven process links and integration points.
WHITE BOX TESTING
White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at
least its purpose. It is purpose. It is used to test areas that cannot be reached from
a black box level.

24
 BLACK BOX TESTING
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as
most other kinds of tests, must be written from a definitive source document,
such as specification or requirements document, such as specification or
requirements document. It is a testing in which the software under test is treated,
as a black box .you cannot “see” into it. The test provides inputs and responds to
outputs without considering how the software works.
UNIT TESTING:
Unit testing is usually conducted as part of a combined code and unit test phase
of the software lifecycle, although it is not uncommon for coding and unit testing
to be conducted as two distinct phases. Test strategy and approach Field testing
will be performed manually and functional tests will be written in detail.
Test objectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
Features to be tested
• Verify that the entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page.
INTEGRATION TESTING
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused
by interface defects. The task of the integration test is to check that components
or software applications, e.g. components in a software system or – one step up –
software applications at the company level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.
ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements. Test Results: All the test cases mentioned above passed
successfully. No defects encountered.

• 8. Tools and Technologies

The development of the Mental Health Journal & Mood Tracker App requires a
variety of tools and technologies to ensure functionality, performance,
scalability, and security. The selected tools span across frontend, backend,

25
database, analytics, and deployment technologies.

1. Frontend Technologies

- Flutter: A cross-platform framework used for developing high-performance

mobile applications for both Android and iOS from a single codebase.
- Dart: The programming language used in Flutter to build the UI and app logic.
- Material Design & Cupertino Widgets: For creating responsive and native-
looking user interfaces for Android and iOS.

2. Backend Technologies

- Node.js: A JavaScript runtime built on Chrome’s V8 engine, used for building

scalable server-side applications.
- Express.js: A lightweight web application framework for Node.js that facilitates
the creation of RESTful APIs.
- Firebase Cloud Functions: Used for backend serverless logic and automation.

3. Database Technologies

- Firebase Realtime Database / Firestore: NoSQL cloud-hosted databases for

storing and syncing data in real-time across users.
- PostgreSQL (optional): A relational database system that may be used for
structured data and advanced querying.

4. Authentication and Security

- Firebase Authentication: Provides secure user authentication using

email/password, Google Sign-In, and other identity providers.

26
- HTTPS & JWT: Ensures secure communication and authenticated API access.

5. Notifications & Scheduling

- Firebase Cloud Messaging (FCM): Enables push notifications to engage users

with reminders and alerts.
- Local Notifications: Used for device-based reminder scheduling.

6. Analytics and AI

- TensorFlow Lite: Lightweight machine learning for on-device sentiment

analysis (optional).
- Google Cloud Natural Language API / IBM Watson: Used for processing and
analyzing user journal entries (optional AI features).
- fl_chart (Flutter package): To visualize data trends and mood patterns in charts
and graphs.

7. Development & Version Control Tools

- Visual Studio Code: Preferred IDE for both frontend and backend development.
- Git & GitHub: Used for version control, source code management, and team
collaboration.

8. Deployment & Hosting

- Firebase Hosting: For hosting web versions or assets if necessary.

- Google Play Store / Apple App Store: Platforms for deploying the mobile app
to end users.

27
The integration of these technologies ensures that the app is robust, scalable,
user-friendly, and secure, providing users with a reliable tool for tracking and
managing their mental health.

9.Coding

=== Flutter Mood Entry Form Code ===

// Flutter (Dart) - Mood Entry Form Widget

import 'package:flutter/material.dart';

class MoodEntryForm extends StatefulWidget {

@override

_MoodEntryFormState createState() => _MoodEntryFormState();

class _MoodEntryFormState extends State<MoodEntryForm> {

String mood = '';

int intensity = 5;

void submitMood() {

print("Mood: $mood, Intensity: $intensity");

// Here you would typically call an API to submit the mood data

28
}

@override

Widget build(BuildContext context) {

return Scaffold(

appBar: AppBar(title: Text("Log Mood")),

body: Padding(

padding: const EdgeInsets.all(16.0),

child: Column(

children: [

TextField(

decoration: InputDecoration(labelText: 'Enter your mood'),

onChanged: (val) => setState(() => mood = val),

),

Slider(

min: 1,

max: 10,

divisions: 9,

label: intensity.toString(),

value: intensity.toDouble(),

onChanged: (val) => setState(() => intensity = val.toInt()),

),

29
 ElevatedButton(

onPressed: submitMood,

child: Text("Submit Mood"),

),

],

),

),

);

=== Input/Output Flow ===

**Sample Input:**

- Mood: "Happy"

- Intensity: 8

**Expected Output (Console or Backend Log):**

Mood: Happy, Intensity: 8

**User Interface Flow:**

30
1. User opens the app and navigates to 'Log Mood' screen.

2. Enters "Happy" in the mood text field.

3. Slides the intensity slider to 8.

4. Presses the "Submit Mood" button.

5. App logs or sends: Mood: Happy, Intensity: 8 to the backend or prints it

locally.

**Backend (Node.js) –

// moodController.js

const admin = require('firebase-admin');

const express = require('express');

const router = express.Router();

// Initialize Firebase Admin SDK

const serviceAccount = require('./serviceAccountKey.json');

if (!admin.apps.length) {

admin.initializeApp({

credential: admin.credential.cert(serviceAccount),

databaseURL: 'https://<your-database-name>.firebaseio.com' // Replace with

your Firebase DB URL

31
 });

const db = admin.firestore();

// POST /mood - Save a mood entry

router.post('/mood', async (req, res) => {

try {

const { userId, mood, intensity, timestamp } = req.body;

if (!userId || !mood || !intensity || !timestamp) {

return res.status(400).json({ error: 'Missing required fields' });

await db.collection('users').doc(userId).collection('moods').add({

mood,

intensity,

timestamp: admin.firestore.Timestamp.fromDate(new Date(timestamp))

});

return res.status(200).json({ message: 'Mood entry saved successfully' });

} catch (error) {

console.error('Error saving mood:', error);

32
 return res.status(500).json({ error: 'Internal server error' });

});

module.exports = router;

Sample API Endpoint**

POST /mood

Request Body:

"userId": "abc123",

"mood": "Happy",

"intensity": 8,

"timestamp": "2025-05-08T10:00:00Z"

33
10. Results

34
 11. Conclusion

The Mental Health Journal & Mood Tracker App successfully addresses the
growing need for digital mental health support tools by integrating key
functionalities like mood logging, journaling, data visualization, and reminders
into a seamless user experience. The project demonstrates the potential of using
cross-platform frameworks such as Flutter, robust backend solutions like
Firebase and Node.js, and AI-enhanced analytics for sentiment analysis and
mood trend detection.

Through intuitive UI design and secure architecture, the app empowers users to
engage in self-reflection, track emotional well-being, and build mental resilience.
The modular approach adopted during development ensures scalability,
maintainability, and ease of enhancement. As mental health awareness becomes
increasingly vital, this application lays the foundation for future integration with
wearables, advanced AI for mood prediction, and therapy-based
recommendations. Overall, the project exemplifies a thoughtful blend of
technology and psychology aimed at fostering emotional well-being.

12. References
1. Google Firebase Documentation – https://firebase.google.com/docs
2. Flutter Official Docs – https://docs.flutter.dev
3. Node.js Documentation – https://nodejs.org/en/docs/
4. MongoDB Documentation – https://www.mongodb.com/docs/
5. Tailwind CSS Docs – https://tailwindcss.com/docs
6. Chart.js Documentation – https://www.chartjs.org/docs/
7. Google Cloud Natural Language API – https://cloud.google.com/natural-
language
8. IBM Watson Natural Language Understanding –
https://www.ibm.com/cloud/watson-natural-language-understanding
9. Android Studio Documentation – https://developer.android.com/studio
10. GitHub Docs for Version Control – https://docs.github.com/

35