A
Project Report
On
“Only Win”
Submitted in Partial Fulfillment of the Requirements for the
Award of the Degree of
Bachelor of Computer Application
Submitted by
Ankit Nishad 202210101310084
Shikhar Verma 202210101310068
Mo Asad 202210101310065
Under the Guidance of
ER. Anuradha Yadav
Assistant Professor
Department of Computer Science & Information Systems
Shri Ramswaroop Memorial University
1
Lucknow – Deva Road, Barabanki (UP)
December, 2024
DECLARATION
I hereby declare that the project report entitled “Only Win” submitted by us to
Shri Ramswaroop Memorial University, Lucknow – Deva Road, Barabanki (UP) is
the partial requirement for the award of the degree of the Bachelor of Computer
Application in Data Science OR Artificial Intelligence is a record of bonafide project
work carried out by us under the guidance of “Anuradha Yadav”. I further declare that
the work reported in this project has not been submitted and will not be submitted either
in part or in full for the award of any other degree in this institute.
Place:
Date:
Signature of students(s)
Signature of students(s)
Signature of students(s)
2
SHRI RAMSWAROOP MEMORIAL UNIVERSITY
Department of Computer Science & Information Systems
Certificate
This is to certify that this Major Project report of B. Tech. Final Year, entitled “Only
Win”, Submitted by Ankit Nishad (202210101310084), Shikar Verma (2022101310068) and
Mo. Asad (20221010131065) is a record of bonafide work carried out by them, in the partial
fulfillment with Degree of Bachelor of Computer Application , Shri Ramswaroop Memorial
University, Lucknow – Deva Road, Barabanki (UP). This work is done during the Academic
Year 2024 – 2045 under my supervision and guidance.
Date:
Guided & Approved By….
Under the Supervision of Project In-charge
ER. Anuradha Yadav Ms. Nidhi Tiwari
(Assistant Professor) (Assistant Professor)
3
Head of Department
Dr. Bineet Kumar Gupta
(Associate Professor & Head)
Acknowledgement
The satisfaction that accompanies that the successful completion of any task would be
incomplete without the mention of people whose ceaseless cooperation made it possible,
whose constant guidance and encouragement crown all efforts with success. We owe a
great many thanks to great many people, who assisted and helped me during and till the
end of the project.
We would like to express our gratitude towards Dr. Bineet Kumar Gupta, Head of
Department - Computer Science & Information Systems, Shri Ramswaroop
Memorial University, Lucknow – Deva Road, Barabanki (UP), for his guidelines and
scholarly encouragement.
We are indebted to Mr. Guide Name – Assistant Professor, Computer Science &
Information Systems of Shri Ramswaroop Memorial University, Lucknow – Deva
Road, Barabanki (UP) for their valuable comments and suggestions that have helped us
to make it a success. The valuable and fruitful discussion with them was of immense help
without which it would have been difficult to present this project in live.
We gratefully acknowledge and express our gratitude to all faculty members and friends
who supported us in preparing this project report.
Finally, this acknowledgement is incomplete without extending our deepest – felt thanks
and gratitude towards our parents whose moral support has been the source of
nourishment for us at each stage of our life.
ANKIT NISHAD (202210101310084)
4
SHIKHAR VERMA (202210101310068)
MO. ASAD (20221010131065)
ABSTRACT
The Earning Application is a web-based platform designed to
streamline the process of task allocation and earning rewards for
completed tasks. The project aims to provide users with a seamless
online system where they can register, log in, and engage in tasks
posted by others to earn rewards. The system also allows task creators
to post, manage, and track task progress.
The application employs Java for backend development, utilizing
technologies like Servlets for dynamic content rendering and handling
business logic. Firebase is integrated as the cloud database solution to
store user data, tasks, and transactions efficiently. The front end is
crafted with XML (Markup language) to define the app's user interface
and layout , ensuring a responsive and intuitive user experience.
Key features include user authentication, role-based access control,
task creation and assignment, and a reward tracking system.
Advanced functionalities like push notifications, task status updates,
and real-time database synchronization are enabled through Firebase.
Security measures such as encrypted user data storage and secure
authentication mechanisms are implemented to protect sensitive
information.
This project aims to create a user-friendly and efficient platform where
users can earn rewards by completing tasks, while task creators
benefit from streamlined task management and monitoring. It
showcases expertise in web development, cloud database integration,
and reward-based application design, delivering a comprehensive
5
solution for task and reward management.
TABLE OF CONTENTS
DECLARATION ii
CERTIFICATE iii
ACKNOWLEDGEMENT iv
ABSTRACT v
LIST OF TABLES vii
LIST OF FIGURES viii
LIST OF SYMBOLS AND ABBREVIATIONS ix
CHAPTER 1: INTRODUCTION 1
1.1 Introduction of the Project
1.2 Objective and Scope of the Project
1.2.1 Specific objective
1.2.2 Scope and Boundary
1.2.3 Detailed features
[Link] Feature 1
[Link] Feature 2
[Link] Feature 3
1.3 Problem Statement
1.4 Methodology
CHAPTER 2: LITERATURE REVIEW
2.1 Previous Research
2.2 Current Trends
CHAPTER 3: DESIGN OF PROJECT MODEL
CHAPTER 4: EXPERIMENTS, SIMULATION & TESTING
4.1 Methodology
4.2 Hardware & Software used
4.3 Testing Technology used
CHAPTER 5: RESULT AND DISCUSSION
6
CHAPTER 6: CONCLUSION AND FUTURE SCOPE
6.1 Conclusion
6.2 Future Scope
References
BIOGRAPHY
LIST OF TABLES
Table No. Title P. No
7
LIST OF FIGURES
Figure No. Title P. No
CHAPTER 1
INTRODUCTION
8
OBJECTIVE:
The main objective of the document is to illustrate the Requirements of
project Earning Apllication. The document gives the detailed
description of both functional and non-functional requirements. It will
also explain about the features of the system interface of the system.
What the system will do, the constraint under which it must operate
and how the system will react to external stimuli. The document is
developed after a number of consultations with team members and
specification of the given project.
2. SCOPE OF THE PROJECT:
The software provide the visitor, customer and administrator a easy
and efficient way to earn money throw online method without any
investment.
Software provides following facilities to customer:
❖ Facilitates easy Earn Money online.
❖ Provides different- different task.
❖ Provides e-mail facility for future correspondence.
❖ Provides Backup facility.
❖ Software provides the following facilities to the User.
9
❖ Look after the payment method.
3. PROJECT DESCRIPTION:
This software is totally self contained and works relatively an efficient
on the package relates to the software. It provides simple database
rather than complex one for high requirement and it provides a good
and easy graphical user interface to both new and naïve as well as
experienced user of the computer.
4. REQUIREMENTS:
(a).FUNCTIONAL REQUIREMENTS
❖ Register - Enter details in application form.
❖ Login - Enter Email and Password.
❖ Select - Select Task .
❖ Earn - Complete task and Earn Coins.
❖ Payment - Redeem coins in different method.
❖ Update - Update transaction history.
(b).NON- FUNCTIONAL REQUIREMENTS:
❖ Tasks - Collection of tasks.
❖ Leaderboard - Highest Earned by User.
10
❖ Profile - Detail of User .
❖ Total Coins - taotal coins that user earn.
❖ Redeem - Redeem your coni to your Paytm or Paypal.
5. MODULE DISCRIPTION:
In this project we have defined different modules to enable the
Eearning Application in successful manner.
i. REGISTER:
The register module contains the application form or registration form
which contains following details.
Name, E-mail id, Password etc.
iii. LOGIN:
The Login module contain the form which contain membership email
and member password.
11
It includes Email and Password
iv. Tasks:
The Tasks module contain list of Tasks, from this list we select the
Tasks which we [Link] also containes another field called as
categories where can select the category of the tasks.
v. Leaderboard:
The leaderboard module contains the highest earn coin by
user ,whatever we shaw about top user.
vi. PAYMENT:
After the earn coins . Then the user is going to reddeem button. So
user has to select the type of transaction wheather Paytm or PayPal.
vii. Transaction History:
The website admin has to maintain the payment record where the
record should be in updated, where how many coins is redeemed by
user. How much amount credited and names of user who redeemd the
coins .
viii. UPDATE:
12
The update module should maintained by the website administrator.
The admin should update each and every process like.
❖ • Number of user registered
❖ • Registered user viewing.
❖ • Redeemed by user.
❖ • Payment affered by user.
UML USECASE DIAGRAM:
Uml provides use case diagram natation to iilustrate the names of use
case and author relationship between them. Use case diagram and
case relationship are secondary in use case work usecase text
document
13
14
UML ACTIVITY PROGRAM
A Uml activity diagram shows sequential and parallel activites in a
process,work flows,data flows and compiler algorithm
ACTIVITY DIAGRAM
UML CLASS DIAGRAM:
15
The Uml class diagram is to illutrates class interfaces ans their
[Link] are used for ststic object modeling, we have already
introduced and used their uml diagram while domain modeling.
16
CLASS DIAGRAM
17
UML SEQUENCE DIAGRAM:
A sequence diagram illustrate akind of format in which each object
18
interact via message. It is generalize between two or more specialized
diagram.
19
20
UML COLLABRATION DIAGRAM:
Communicaton diagram illustrate that object interact on a graph or
network format in which object can be placed where an thw diagram.
In collabration diagram the object can be placed in anywhere on the
daigram. The collabration comes from sequence diagram.
21
22
UML STATE CHART DIAGRAM:
A Uml state machine represents the interaction events and states of an
object and behaviour of an object in reaction to an event.. Transaction
shown as allows labelled with their event. It is included with initial
psedo state and fins end state.
UML COMPONENT DIAGRAM:
Components are slightly fuzzy concept in this Uml,because both class
and components can be used to model the something .
23
24
UML DEPLOYEMENT DIAGRAM:
Deployement diagram shows the assignment of concrete software
artifact to computational nodes. It shows the deployement of software
elements to the physical elements. Deployement diagram are useful to
communicate or deployement architecture .
25
26
CONCLUSION:
Thus the project for Earning Application has been successfully
executed and codes are generated.
SOFTWARE REQUIREMENTS SPECIFICATIONS
[Link] :-
The Earning Application is designed to simplify earning money online
without requiring any initial investment. This platform connects task
creators with task performers, enabling a streamlined process for
posting and completing tasks. It automates the flow of task allocation,
progress tracking, and payment processing to ensure efficiency and
reliability.
Automation plays a significant role in modern applications by reducing
manual effort and enhancing accuracy. For instance, systems like
autopilots in aircraft, smart home systems, and automated business
processes showcase how automation can transform operations.
Similarly, this Task Earning Application introduces automation into the
task management domain, offering users an intuitive system to earn
rewards seamlessly.
Task performers can select tasks based on their preferences, complete
them, and earn money, while task creators can post tasks, track
progress, and make payments securely through the platform. This
eliminates the complexities of manual task delegation and reward
distribution, providing a fast and error-free experience.
The purpose of this project is to deliver a user-friendly and efficient
platform that automates the process of task earning, ensuring
satisfaction for both task creators and performers.
27
1.1 Purpose
Today’s world relies heavily on software applications to manage and
streamline daily operations. From business applications to personal
software, the focus has shifted toward creating reliable, efficient, and
scalable systems. This project embraces the same principle by
introducing a task earning platform that automates task posting,
performance tracking, and reward management.
The primary goals of the system include:
⦁ Simplifying Task Management: Automating task allocation and
completion to save time and reduce errors.
⦁ Enabling Online Earning Opportunities: Offering individuals a
platform to earn money online without upfront investments.
⦁ Improving Communication: Facilitating smooth interactions
between task creators and performers through notifications and
real-time updates.
Manual processes of finding and assigning tasks are often slow and
inefficient. By introducing this automated platform, users can manage
tasks, track progress, and process payments faster, saving time and
resources.
1.2 Scope
The name of the project is Earning Application. This platform is
designed for users looking to earn rewards by completing tasks and for
task creators who need their work completed efficiently. The following
functionalities are provided:
Features for Task Performers (Users):
⦁ View and select tasks based on preferences and eligibility.
28
⦁ Receive detailed descriptions and requirements for each task.
⦁ Track task progress and deadlines in real-time.
⦁ Securely receive payments upon task completion.
⦁ Communicate with task creators via in-app messaging.
⦁ Access performance statistics and history.
Features for Task Creators:
⦁ Post tasks with detailed requirements and deadlines.
⦁ Review task performer profiles and assign tasks accordingly.
⦁ Track task progress and receive real-time updates.
⦁ Process payments securely through the platform.
⦁ Manage task history and maintain records of completed tasks.
Limitations of the System:
⦁ Tasks cannot be canceled once assigned.
⦁ The platform does not provide legal mediation in case of
disputes.
⦁ Any inaccuracies in task descriptions are the responsibility of the
task creator.
29
Definitions ,Acronyms and Abbreviations
1. Task Performer (User): The individual who completes tasks
to earn rewards.
2. Task Creator: The individual or organization that posts tasks
for others to complete.
3. PIN Number: A unique identifier for task performers and
creators to access the system securely.
4. References
⦁ Firebase official documentation for database integration.
⦁ Java Server Pages (JSP) and Servlets programming resources.
⦁ Online articles and research on task management systems and
earning platforms.
[Link]
⦁ Firebase official documentation for database integration.
⦁ Java Server Pages (JSP) and Servlets programming resources.
⦁ Online articles and research on task management systems and
earning platforms.
The following subsections provide a complete overview of the
specifications and requirements for the Task Earning Application. This
document outlines the functionalities, limitations, and technical
requirements for the platform, ensuring it meets the needs of both
task performers and creators.
30
DFD
31
2. Overall description
In this module, we define the overall description of the software Task-
Earning Application. This includes the importance of the product, user
characteristics, general constraints, assumptions, and dependencies.
3.1 Product Perspective:
This software is completely self-contained and operates efficiently
compared to other task-based earning platforms. It features a
straightforward database, tailored for moderate requirements, and
provides an intuitive graphical user interface. It is designed to cater to
both new, inexperienced users and seasoned professionals.
3.2 Product Functions:
The following use case diagram provides complete information on how
the product operates. The Task-Earning Application performs the
following functions:
User Identification: Register and authenticate users securely.
Select Task Services: Users can browse and select available tasks
based on their preferences or skills.
Record Task Completion: Logs the details of completed tasks for
individual users.
Manage Earnings: Tracks and calculates earnings for completed tasks.
Search for Available Tasks: Allows users to search for tasks using
filters like category, payment, or deadlines.
Evaluate Performance: Prepares reports evaluating user performance
or success rate in tasks.
Display User Dashboard: Provides a summary of user activity,
32
earnings, and available tasks.
USE CASE DIAGRAM
3.3 Performance Requirements:
⦁ Good Working PC: A PC with all the necessary hardware
interfaces is required for smooth operation.
⦁ Handles Medium-Size Databases: Designed to manage moderate
volumes of user and task-related data.
⦁ Should Not Be Overloaded: Ensures optimal performance even
during peak usage.
⦁ Menu Response Time: Menu navigation will respond within 3
seconds.
⦁ Task Search Response: Searching for tasks will take no more
than 3 [Link] Update and Retrieval: The system updates
and retrieves data from the database within 2 seconds.
⦁ Prompt Display Time: Pop-up messages (e.g., confirmations) will
appear within 2 seconds.
3.4 Design Constraints:
⦁ Browser Compatibility: The system requires a browser
supporting Java, such as Netscape Navigator v4.0 or higher, or
Internet Explorer.
⦁ Java Environment: Java is used to secure transactions and
protect against threats like viruses, worms, and hacking
attempts.
⦁ Fault Tolerance and Compliance: Designed to adhere to industry
33
standards while being fault-tolerant.
⦁ Menu-Driven Interface: The application uses a menu-driven
interface navigable via mouse or keyboard.
⦁ Confirmation and Error Handling:
i. Confirmation messages are shown after each action, input, or
system error.
ii. Input errors or system errors are identified and displayed
promptly.
3.5 Attributes:
⦁ Reliability: The system undergoes thorough testing to minimize
errors before deployment.
⦁ Maintainability:
i. A comprehensive user and system manual is provided.
ii. Modular design allows for easy updates or modifications as
requested.
⦁ Security:
i. Only administrators can modify user and task-related details.
ii. Secure login ensures no unauthorized access.
iii. Regular users cannot access administrative functions.
iv. Deletion actions require confirmation to prevent accidental data
loss.
3.6 Other Requirements:
⦁ Future Expansion: The system is designed with
scalability in mind, allowing future enhancements as
new features or technologies emerge.
34
⦁ Technological Updates: Provisions for integrating
upcoming technologies to stay competitive.
⦁ Scalable Design: Supports system expansion to handle
increased user load or new features.
1.1 Introduction of the Project:
This project, "Task-Earning Application", aims to revolutionize how users find and
complete tasks for earnings. The system integrates modern features such as user
authentication, intuitive interfaces for task browsing and management, and a secure
platform for handling transactions. It creates a bridge between task providers and earners
while offering administrators full control over task listings, user activity, and earnings.
As the gig economy grows, the need for a robust task-earning platform becomes evident.
This system leverages cutting-edge backend technologies and responsive design to ensure
an efficient, secure, and user-friendly experience for all stakeholders.
35
CHAPTER 2
LITERATURE REVIEW
Previous Research
The evolution of task-earning platforms can be traced back to traditional offline systems
of employment and freelancing, which were often limited by geographical constraints,
high operational costs, and inefficiencies in task matching. With the rise of the gig
economy, platforms like Upwork and Fiverr introduced digital solutions for connecting
task providers with workers. However, these platforms often cater to large-scale
operations, leaving smaller, personalized markets underserved.
Previous research identified the following gaps in existing solutions:
1. Lack of Personalization: Most platforms offer generic services, lacking features
like skill-based recommendations, personal dashboards, or localized
opportunities.
2. Administrative Complexity: Task providers and administrators frequently face
challenges managing listings, tracking task completion, and handling payments
due to the absence of simple, dedicated tools.
3. Exclusion of Local or Niche Markets: Smaller or local task providers often
struggle to compete on major platforms, leading to limited visibility and
engagement.
These challenges highlight the need for a focused task-earning application that bridges
36
these gaps, offering solutions tailored to diverse users and promoting inclusivity and
efficiency.
2.2 Current Trends
Several technological and societal trends have shaped the design and
development of task-earning platforms:
1. Rise of Mobile-First Platforms:
The increasing reliance on smartphones for work-related activities has raised user
expectations for mobile-responsive, intuitive applications. Task-earning platforms must
prioritize mobile-friendly designs for seamless on-the-go usage.
2. Cloud Computing:
Cloud-based technologies enable secure, scalable, and cost-effective solutions for
managing large volumes of task and user data. Leveraging cloud systems ensures high
availability and reliability for users and administrators alike.
Shift Towards Sustainability:
The global push for sustainable practices encourages the adoption of digital workflows,
reducing reliance on paper-based processes or physical interactions. A task-earning
application aligns with this by digitizing task management and communication.
Focus on User-Centric Design:
Modern applications prioritize simplicity and personalization. Features like dynamic task
categorization, skill-based recommendations, and user-friendly dashboards are becoming
standard expectations.
37
Integration of Data Analytics:
Data-driven insights enable administrators and task providers to make informed
decisions. Future iterations of task-earning applications can incorporate analytics to
identify trends, evaluate user performance, and optimize task recommendations.
By understanding these trends, the proposed system aims to deliver a task-earning
platform that is scalable, user-focused, and aligned with emerging technological and
societal needs.
CHAPTER 3
DESIGN OF PROJECT MODEL
38
3.1 System Architecture
The Earning Application is based on a multi-tier architecture that ensures modularity,
scalability, and maintainability:
1. Presentation Layer:
This layer is responsible for the user interface and interaction.
Technologies used: Java, XML.
Includes features like login, registration, redeem, and leaderboard.
2. Application Layer:
Handles task logic, including user authentication, payment, and payment processing.
Technologies used: Java , and SDK.
3. Data Layer:
39
Manages database operations and ensures secure data storage.
Database: NoSQL (Firebase).
Handles tables for users, tasks, ads, and payment.
---
3.2 UML Diagrams
Class Diagram
Represents the core classes, their attributes, and methods. For example:
User Class: Attributes include userID, email, password, role.
Book Class: Attributes include bookID, name, author, price, category.
Order Class: Attributes include orderID, userID, bookID, quantity.
40
Sequence Diagram
Illustrates the interaction between actors and the system for common scenarios:
User Login: User → Servlet → Database → Response.
Redeem Coin: Admin → Add Coin Servlet → Database → Success Message.
Use Case Diagram
Defines the roles (Admin, User) and their interactions with the system. For example:
Admin: Add, edit, delete tasks; view tasks.
User: Register, browse tasks, place orders.
41
CHAPTER 4
EXPERIMENTS, SIMULATION & TESTING
Methodology
Development Stages:
1. Requirement Analysis: Identified user needs and system goals.
2. System Design: Created wireframes, UML diagrams, and database schemas.
3. Implementation: Coded the backend (Java) and frontend (XML for design and
layout).
4. Testing: Verified functionality, usability, and performance.
42
Testing Stages:
Unit Testing: Validated individual components like login and transaction history.
Integration Testing: Ensured seamless interaction between modules (e.g., database
queries).
System Testing: Tested the complete system under realistic conditions.
4.2 Hardware & Software Used
Hardware:
Processor: Intel Core i5 or equivalent.
RAM: 8GB minimum.
Storage: 1TB HDD/256GB SSD.
43
Software:
Backend: Java (JDK 8+), SDK.
Frontend: XML.
Database: FIREBASE
IDE: Android Studio.
4.3 Testing Technology Used
Unit: For unit testing Java code.
Postman: For API testing.
Selenium: For automated UI testing.
44
FIREBASE Workbench: For database testing and query validation.
4.4 Coding Part
[Link]
package [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
public class MainActivity extends AppCompatActivity {
ChipNavigationBar chipNavigationBar;
private Fragment fragment = null;
@Override
protected void onCreate(Bundle savedInstanceState) {
[Link](savedInstanceState);
setContentView([Link].activity_main);
chipNavigationBar = findViewById([Link]);
[Link]([Link], true);
45
getSupportFragmentManager().beginTransaction().replace([Link],
new HomeFragment()).commit();
[Link](new
[Link]() {
@Override
public void onItemSelected(int i) {
if (i==[Link]){
fragment =new HomeFragment();
} else if (i==[Link]) {
fragment =new LeaderboardFragment();
} else if (i==[Link]) {
fragment =new ProfileFragment();
}
if (fragment!=null){
getSupportFragmentManager().beginTransaction().replace([Link],fr
agment).commit();
}
}
});
}
}
[Link]
package [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
46
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
public class SignUpActivity extends AppCompatActivity {
ActivitySignUpBinding binding;
FirebaseAuth auth;
FirebaseFirestore firestore;
ProgressDialog progressDialog;
@Override
protected void onCreate(Bundle savedInstanceState) {
[Link](savedInstanceState);
binding = [Link](getLayoutInflater());
setContentView([Link]());
auth = [Link]();
firestore = [Link]();
progressDialog = new ProgressDialog(this);
[Link]("Creating Your Account");
[Link]("Your Account is creating");
47
[Link](new [Link]()
{
@Override
public void onClick(View view) {
String name = [Link]().toString();
String email = [Link]().toString();
String password =
[Link]().toString();
if ([Link]()){
[Link]("Enter your name");
}
else if ([Link]()){
[Link]("Enter email");
}
else if ([Link]()){
[Link]("Enter Password");
}
else {
[Link]();
storeUserData(name, email, password);
}
}
});
[Link](new [Link]() {
@Override
public void onClick(View view) {
Intent intent = new Intent([Link],
[Link]);
startActivity(intent);
}
});
48
private void storeUserData(String name, String email, String
password) {
[Link]([Link]().toString(
),[Link]().toString()).addOnCompleteListener(new
OnCompleteListener<AuthResult>() {
@Override
public void onComplete(@NonNull Task<AuthResult> task) {
if ([Link]()) {
String referCode =
[Link](0,[Link]("@"));
UserModel model = new UserModel(name, email,
password,
"[Link]
[Link]/o/[Link]?alt=media&token=2cba0cc7-d09f-4463-8f21-
d4be50575b7e",
referCode,
"false",
5,
5,
5);
String id = [Link]().getUser().getUid();
[Link]("users").document(id).set(model).addOnCompleteListe
ner(new OnCompleteListener<Void>() {
@Override
public void onComplete(@NonNull Task<Void> task)
{
if ([Link]()){
[Link]();
Intent intent = new
Intent([Link], [Link]);
startActivity(intent);
49
finish();
}
else {
[Link]();
[Link]([Link],
[Link]().getLocalizedMessage(), Toast.LENGTH_SHORT).show();
}
}
});
}
else {
[Link]([Link],
[Link]().getLocalizedMessage(), Toast.LENGTH_SHORT).show();
}
}
});
[Link](new [Link]() {
@Override
public void onClick(View view) {
Intent intent = new Intent([Link],
[Link]);
startActivity(intent);
finish();
}
});
}
}
[Link]
package [Link];
import [Link];
50
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link].R;
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
import [Link];
public class ProfileFragment extends Fragment {
FragmentProfileBinding binding;
FirebaseAuth auth;
FirebaseFirestore firestore;
FirebaseStorage storage;
Uri profileUri;
51
ProgressDialog progressDialog;
Dialog dialog;
public ProfileFragment() {
// Required empty public constructor
}
@Override
public void onCreate(Bundle savedInstanceState) {
[Link](savedInstanceState);
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup
container,
Bundle savedInstanceState) {
// Inflate the layout for this fragment
binding = [Link](inflater, container,
false);
auth = [Link]();
firestore = [Link]();
storage = [Link]();
progressDialog = new ProgressDialog(getContext());
[Link]("Profile Uploading");
[Link]("We are uploading your profile");
dialog = new Dialog(getContext());
[Link]([Link].loading_dialog);
[Link]();
loadUserData();
52
[Link](new [Link]()
{
@Override
public void onClick(View v) {
Intent intent = new Intent();
[Link](Intent.ACTION_GET_CONTENT);
[Link]("image/*");
startActivityForResult(intent, 2);
}
});
[Link](new
[Link]() {
@Override
public void onClick(View v) {
startActivity(new Intent( Intent.ACTION_VIEW,Uri.
parse("[Link]
}
});
[Link](new [Link]() {
@Override
public void onClick(View v) {
startActivity(new Intent( Intent.ACTION_VIEW,Uri.
parse("[Link]
}
});
[Link](new [Link]() {
@Override
public void onClick(View v) {
String shareBody = "Hey, I am using best Earning App";
Intent intent = new Intent(Intent.ACTION_SEND);
[Link]("type/plain");
[Link](Intent.EXTRA_TEXT,shareBody);
startActivity(intent);
}
});
[Link](new
53
[Link]() {
@Override
public void onClick(View v) {
Intent intent = new Intent(getContext(),
[Link]);
startActivity(intent);
}
});
[Link](new [Link]() {
@Override
public void onClick(View v) {
[Link]();
Intent intent = new Intent(getContext(),
[Link]);
[Link](Intent.FLAG_ACTIVITY_CLEAR_TOP);
startActivity(intent);
}
});
return [Link]();
private void loadUserData() {
[Link]("users").document([Link]().getUid
())
.get().addOnSuccessListener(new
OnSuccessListener<DocumentSnapshot>() {
@Override
public void onSuccess(DocumentSnapshot
documentSnapshot) {
UserModel model =
[Link]([Link]);
if ([Link]()) {
[Link]([Link]());
[Link]([Link]());
54
[Link]()
.load([Link]())
.placeholder([Link])
.into([Link]);
[Link]();
}
});
}
@Override
public void onActivityResult(int requestCode, int resultCode,
@Nullable Intent data) {
[Link](requestCode, resultCode, data);
if (requestCode==2){
if (data!=null){
profileUri = [Link]();
[Link](profileUri);
updateProfile(profileUri);
}
}
}
private void updateProfile(Uri profileUri) {
[Link]();
final StorageReference reference =
[Link]().child("profile").child([Link]()
.getUid());
[Link](profileUri)
.addOnSuccessListener(new
OnSuccessListener<[Link]>() {
55
@Override
public void onSuccess([Link]
taskSnapshot) {
[Link]().addOnSuccessListener(new
OnSuccessListener<Uri>() {
@Override
public void onSuccess(Uri uri) {
[Link]("users").document([Link]().getUid
())
.update("profile",[Link]()
);
[Link](getContext(), "Profile
updated", Toast.LENGTH_SHORT).show();
[Link]();
}
});
}
});
}
}
CHAPTER 5
RESULT AND DISCUSSION
Summary of Results
56
The system successfully meets its objectives:
Admins can manage task listings and categories efficiently.
Users can browse, search, and task seamlessly.
Secure authentication ensures user data protection.
Significance
Improved user satisfaction due to the intuitive interface and fast responses.
Enhanced productivity for administrators with easy management tools.
Potential Improvements
Introduce analytics for admin insights .
Add multi-language support for wider accessibility.
CHAPTER 6
CONCLUSION AND FUTURE SCOPE
57
The Earning Appliction effectively bridges the gap in online earnng method by providing
a feature-rich, user-friendly platform. It empowers users to complete task and redeem
coin easily.
6.2 Future Scope
1. Integration of Payment Gateway: For quick online transactions.
2. Mobile iOS Development: Extending functionality to iOS platforms.
3. Advanced Recommendation Engine: Using AI to suggest tasks based on user
preferences.
4. Support for Payment: Enabling direct pay and recieve from any platform.
REFERENCES
58
1. Books :
⦁ Rajkumar, R., & Kumar, P. (2021). Advanced Concepts in Java Development.
Wiley Publications.
This book provided insights into Java technologies, particularly useful for backend logic
and API integration in Android Studio.
⦁ Choudhary, S., & Agarwal, D. (2018). Database Design Principles. McGraw-Hill
Education.
A comprehensive guide that helped in designing and normalizing the database for the
task-earning application.
⦁ Gupta, A. (2020). Mobile Application Development and Design. Springer.
This book covered essential components of mobile application architecture and UI/UX
design, which shaped the project’s structure and objectives .
2. Websites and Online Tutorials:
⦁ GeeksforGeeks. Java and Android Basics.
[Link]
A valuable resource for understanding core Android development concepts, including
Activities, Intents, and UI elements.
⦁ Firebase Documentation.
[Link]
Provided detailed guidance on integrating Firebase for user authentication and database
management.
59
⦁ W3Schools. XML, Material Design, and Responsive Design Tutorials.
[Link]
Assisted in designing responsive and visually appealing interfaces for the task-earning
app.
3. Open-Source Tools and Frameworks:
⦁ Android Studio Official Documentation.
[Link]
Provided essential knowledge for setting up and managing the Android Studio
environment.
⦁ Retrofit Library Documentation.
[Link]
Guided API integration for seamless communication between the client-side app and the
backend server.
⦁ Selenium WebDriver Documentation.
[Link]
Used as a reference for testing and ensuring functionality across various Android devices.
4. Research Papers and Articles:
⦁ Sharma, K., & Patel, V. (2022). "A Study on Secure Authentication in Mobile
Applications."
International Journal of Computer Science and Technology.
This paper contributed to designing a secure login and user authentication mechanism
60
using Firebase Authentication.
⦁ Singh, M. (2019). "Trends in Mobile Application Technology."
Journal of Mobile Application Development, 45(3), 123-134.
Helped in understanding modern trends influencing the mobile app industry, such as real-
time notifications and user-centric features.
5. Videos and Tutorials:
⦁ CodeWithHarry. Android Studio Basics and Advanced Tutorials. Available on
YouTube: [Link]
These video tutorials clarified the implementation of Android features like RecyclerView,
LiveData, and Navigation Components.
⦁ FreeCodeCamp. Building Mobile Applications with Firebase.
[Link]
Guided the integration of Firebase services for real-time task updates and secure data
storage.
6. Practical Applications and Online Examples:
⦁ GitHub Repositories on Task Management Projects:
[Link]
Provided inspiration for structuring code, modular design, and implementing features like
task notifications and filtering.
⦁ Stack Overflow Discussions:
[Link]
Aided in troubleshooting and debugging during the development process, particularly
61
with Android-specific issues such as Gradle configuration and UI errors.
BIOGRAPHY
Ankit Nishad was born at Azamgarh, UP in India. He
received Intermediate with science branch in 2022 from
New Cambridge Public School Azamgarh UP. Presently
he is persuing BCA. Degree from Shri Ramswaroop
Memorial University Barabanki.
Shikhar Verma was born at Barabanki, UP in India. He
received Intermediate with science branch in 2021 from
Pioneer Montessori Inter College Barabanki UP.
Presently he is persuing BCA. Degree from Shri
Ramswaroop Memorial University Barabanki.
Mohabbad Asad was born at Amethi, UP in India. He
received Intermediate with science branch in 2022 from
Amethi UP. Presently he is persuing BCA. Degree from
Shri Ramswaroop Memorial University Barabanki.
62
63