My Task Final Report

MY TASK – JUST NOTE IT!
APPENDIX 1
TO DO LIST MOBILE APPLICATION
TITLE OF THE PROJECT

MY TASK- JUST NOTE IT!
A PROJECT REPORT
Submitted by
TEAM LEADER: SHAAN TYAGI (20BCS1023)

DAKSH AGARWAL (20BCS1026)
BADAL JHA (20BCS1056)
in partial fulfilment for the award of the degree of
BACHELOR OF ENGINEERING
IN
COMPUTER SCIENCE
Chandigarh University
MAY 2022
MEMBERS: 1
SHAAN TYAGI (20BCS1023)
Specimen
SOME PERFORMANCE ASPECTS CONSIDERATIONS OF A

CLASS OF ARTIFICIAL NEURAL NETWORK
A PROJECT REPORT
Submitted by
TEAM LEADER: SHAAN TYAGI (20BCS1023)

in partial fulfilment for the award of the degree of
BACHELOR OF ENGINEERING
IN
COMPUTER SCIENCE
Chandigarh University
MAY 2022
MEMBERS: 2
APPENDIX 2
MY TASK- JUST NOTE IT!
BONAFIDE CERTIFICATE
Certified that this project report “MY TASK- JUST NOTE IT!” is the bonafide
work of “DAKSH AGARWAL, SHAAN TYAGI, BADAL JHA” who carried out
the project work under teacher supervision.
SIGNATURE
SUPERVISOR
Dr. Puneet Prasad
Submitted for the project viva-voce examination held on

For ON20BCS- “20 – MAY – 2022” and For PH20BCS “19 – MAY – 2022”
INTERNAL EXAMINER EXTERNAL EXAMINER

ANANDITA JAMWAL (for PH20BCS)
PRIYA BATTA (for ON20BCS)
MEMBERS: 3
ACKNOWLEDGEMENT
We would like to express our heartiest gratitude to Chandigarh University,

Mohali, Punjab and the department of Computer Science and Engineering for
providing us the great opportunity to work on a project, which has enhanced our
technical experience and helping us to step a way ahead to be ready for
contributing to the society with our project.
We would also like to thank our project teacher (Supervisor) Mrs. Priya Batta
(E4978), who always guided us time to time during the progress of the project.
Under her guidance we have learnt about the software development and the
various stages necessary to follow to accomplish the task.
We would like to extend our heartiest gratitude to our project Co-Supervisor

Mr. Puneet Prasad Singh (12181). Under his guidance we have learnt about the
various domains and technologies by which we could achieve our task. He has
always motivated and been so humble to us throughout the journey.
Further we would like to thank each and every member of the team as their
efforts only have brought this project to the level of accomplishment which
gave a sense of achievement at the end.
MEMBERS: 4
TABLE OF CONTENTS
CHAPTERS PAGE NUMBER
CHAPTER 1: INTRODUCTION
CHAPTER 2: LITERATURE
SURVEY
CHAPTER 3: DESIGN FLOW/

PROCESSES
CHAPTER 4: RESULT ANALYSIS

AND VALIDATION
CHAPTER 5: CONCLUSION AND

FUTURE WORK
LIST OF FIGURES
FIGURE NUMBER DESCRIPTION PAGE NUMBER
1 Firebase Cloud Database
2 Java Vs Kotlin Compilation
Speed
3 Firebase Authentication
System
4 Prototype model
5 Evolutionary Model
6 Spiral Model
7 Incremental Model for My
Task Application
8 Data Flow Diagram
9 ER Diagram
10 Class Diagram
MEMBERS: 5
11 Sequence Diagram
12 Collaboration Diagram
13 Navigation Header
14 Navigation Menu
15 Content Note details
16 Login Page
17 Register Details
18 Firebase Console
19 Login Accounts in Firebase
20 Note details in firebase
21 Firebase Analytics 1
22 Firebase Analytics 2
23 My Task Dashboard
24 Play Console Analytics 1
25 My Task on Play Store
LIST OF FIGURES
1. Table of Contents………………………………………… Page No. 4

2. List of Figures….………………………………………… Page No. 4
3. Abbreviations……………………………………………... Page No. 6
4. Table of Timeline…………………………………….......... Page No. 9
MEMBERS: 6
ABSTRACT
We have created a to-do list mobile application using android development with many
functionalities like taking notes and maintain privacy using authorization system of firebase
utilities and google services. So, every user can login using his/her account if any, or create a
new account. To do list application will provide the user authentication system which will
facilitate the user to keep his data or notes private. He will be able to sync the data using his
login credentials. This kind of application is also being provided in the android mobile
phones but does not provide the User Authentication System to keep the data Private and
safe. There is also some extra functionalities like every individual note should be in float
mode and only take the required area in which we can see the whole list. Colors of the notes
should be varying so user can easily find their note and layout should seen more colorful.
Apart from those we will upload this application on play store so anyone with android mobile
phone can download this application and use it.
MEMBERS: 7
ABBREVIATIONS
ABBREVIATION WORD
App. Application
Approx. Approximately
Etc. Etcetera
Nav. Navigation
SDLC Software development Life Cycle
SRS Software Requirement Specification
Intro. Introduction
Stats. Statistics
ER Entity Relationship
b/w Between
Diff. Different
MEMBERS: 8
CHAPTER 1: INTRODUCTION
NEED FOR THIS APPLICATION
In this modern era when everything is too fast, the quantity and speed of providing
knowledge and information is also increasing. Hence, there is no time to write all this info
with pen and paper. To solve this problem there is a need of some technology or software
which can copy the given information in minimum time. The second issue is of privacy.
Sometimes, there are some information that is very crucial or secret so, we do not want to
store it in a place where anyone can access it. So, we have create an application where all
your information are stored in secure cloud storage and only you can access the information
through your login details.
PROBLEM IDENTIFICATION
 There are many less applications or software, which can store our information like
notes, tasks or lists privately. Most of the applications present in the Android
smartphones can store the notes but they can be access by anyone and there is no
security to protect these notes.
 Most of the note taking applications store the notes the physical memory of the phone
or in any secondary device connected to the device like pen drive, SD Card etc. But in
My Task application the user can store his/her notes dynamically on the cloud storage
from where he/she can access these info in any device using their credentials.
 Generally, these note taking applications are very complex and have many options so,
sometimes the user cannot understand the features of the application but My Task app
is very user friendly and have general features which is required to take notes.
TASK IDENTIFICATION
 Create one to do list android application, which provides the facility of sync the notes
using email and password.
 It also provides the security as it will ask for the authentication to sync the notes so
that other person cannot access the confidential data of the another person.
 Notes should be stored in such an order that it can User can find the required note and
differentiate them easily.
MEMBERS: 9
TIMELINE
The whole project completed in the 2 months duration. According to the Software
Development Life Cycle, every project divided into 6 stages. Similarly, the time taken to
complete each stage in project making is given below:
 Stage 1: Planning
In this stage, we have to check that the selected project can be completed in required
timeframe, is feasible or not, check the requirements and then analyse them.
Generally this stage take 10 to 15 days to complete for bigger projects but for our
project planning takes only 4 days.
 Stage 2: Defining
Once the requirement analysis is done the next step is to clearly define and document
the product requirement and get them approved from the supervisor and co
supervisor.
This is done through an SRS document which consist of all the product requirements
like hardware and software requirements.
The time taken to complete this stage is approximately 1 week to 10 days.
 Stage 3: Designing
Based on the requirements specified in Software Requirement Specification (SRS
Document), usually more than one design approach for the product architecture is
purposed and documented in a Design Document Specification.
To take the idea of designing, we have try many note taking application like Google
Notes, Take Notes, Notes etc.
The time taken to complete this stage is approximately 7 days.
 Stage 4: Building
This is the longest and hardest stage of the software development life cycle. In this
stage, actual coding has been done. The code has been written according to the design
document specification.
To write the code efficiently we have to watch many video tutorials of Advance Java
and Android Development.
MEMBERS: 10
The time taken in building process is approx. 3 to 4 weeks.
 Stage 5: Testing
In this stage every functionality is tested. Actually, this stage is the subset of all the
stages. There is a proper order of this Testing phase. First we have to test each
functionality and code individually and separately from one another. Then after that
integrated testing has been done. In this testing, two or more functionalities are
merged and then test them as one unit. Finally, the project testing is done in which
whole software tested.
To test the My Task Application 3 to 4 days has been taken.
 Stage 6: Deployment
Once our app. is tested and ready to be deployed, it is released formally on the play
store. This deployment is happens in stages like we have to create an app bundle in
which all the codes of application is stored and then publish it on the play console.
The whole process takes 2 to 3 days to complete. Once all these 6 stages is completed,
the application can be installed from play store.
The time taken to make the Application and timeline to make different components of
the project is as follows:
Task Time taken in days
Planning 4
Preparing Documentation 5
Building Home Page 5
Building Navigation Bar 3
Building Layout Bar 6
Building Add Notes Page 7
Building Authentication System 5
Testing 4
MEMBERS: 11
Launch Application 4
Deployment Testing 7
Table 1
ORGANIZATION OF THE REPORT:
The report is organized in different chapter. In each chapter we have different things related
to projects like what language we have used, from which literature we have taken references,
data flow of information in the application etc.
Topics you will read in further chapters:
 Literature Survey
 Design Flow and Processes
 Results analysis and validation
 Conclusion and future work
MEMBERS: 12
CHAPTER 2 LITERATURE SURVEY

From the interview/survey results and the themes I extracted from them, I was able to
develop a list of potential solution based on users’ needs:
 Set some constraints on social media, apps, and online distractions. (My research indicates
that users are heavily distracted in this area.)
 Manage time on tasks, then validate time spent. (My research shows that users often lose
track of their time and delay work.)
 Generate a report showing where we spend our time on tasks. (Users want to know better
how their time is spent and how to improve their efficiency.)
 Make it easy for users to manage to-do lists, track time and set constraints in one place.
(Users typically depend on different tools to help organize tasks and track time.)
 Add the ability to prioritize tasks via deadline. (Users wish to prioritize to-dos mainly based
on deadlines.)
 Add the ability to easily add tasks and to search to-do lists. (Users want be able to easily
find to-do items.)
 Reduce distractions from mobile by allowing device settings to be synced from desktop.
(Users want to have data sync cross platform.)
It’s very tempting to include many functions in our quest to help users, but all those functions
might not lead us toward the target we’re aiming for. The Moscow method helps to set the
path of product planning and trim down the scope we need for a minimum viable
product(MVP). The point is to get the product out for real-world testing so we can have
feedback and continue iterating the product
Social media and other easily accessible online distractions make it hard for us to stay
focused on our tasks and make it difficult for us to do our work efficiently.Also, constantly
switching between tasks may give us the false feeling that we are being productive when we
are, in fact, not. It’s more important for us to prioritize tasks and work on those that are most
important, rather than focusing on deleting small items from our todo list just for the sake of
appearances. The goal of this app is to help us become more aware of how we spend time in
the process of doing those tasks and how productive that time is.
It can help set some constraints on social media to reduce distraction and track the time we
spend working on the todo items. When we have a better sense of the estimated time we’ll
need to spend on our tasks, along with the validated time spent on the items for reference or
MEMBERS: 13
personal/team reviews, we are able to manage our daily routines more efficiently. Some
people resist this kind of structure, however. They think it will stymie their creativity or
prevent them from being flexible with their working day. For time management expert David
Allen – whose book Getting Things Done: The Art of Stress-Free Productivity has made him
a cult figure in the field –these free-spirited types are plain wrong. He believes anyone with a
full schedule and no structure will struggle to cope. A system is needed – and scribbled notes
on hands won’t cut it. It’s not enough to scrawl “bank” or “Mum” on a Post-it note, says
Allen – you need more detail. Is it an email, a visit or a phone call, and for what purpose? If
your to-do list isn’t clear and to the point, your tasks probably won’t get done – and they
certainly won’t be prioritized. Detail isn’t the only important factor, however: you also need
to be realistic about how long things will take if you want to construct a workable timetable
for the day. That means factoring in the potential for floating off onto social media or other
distractions if you know you’re susceptible.
FINDINGS FROM DIFFERENT SIMILAR APPLICATIONS

There are several similar applications available on the play store which have also tried their
best to give a good application to the people. But, they haven’t kept in mind about the safety
and privacy of the user’s data.
Some application are just a normal note pads where user is adding his data and saving it.
Whereas in some applications it is found that developers have made a very good application
which has kept in mind about the appearance of the application but didn’t work on the safety
and privacy of the user.
But it suddenly started deleting a lot of data, for example all the lists were gone, then the
headings were gone, all the things wrote were gone.
The app just randomly lost everything I had lists and notes on. Nobody deleted anything, so I
can't restore trashed items. They all just vanished.
In some applications it was seen as there is a single main activity in which all the process is
happening, which sometimes may bore the user and withdraw his interest from the
application. Which may lead to the uninstallation of the application from their devices.
The other findings were that applications are using a single list of the notes which does not
seem attractive and the user may find it difficult to trace the notes when there are so many
notes in the applications.
In some applications after adding the notes, the notes is randomly saved among all the notes.
Due to which he is not able to recognize which is the new note and which is the old one.
There are applications which have not used a title tab in every note, which may not be
convenient for the user to use the application because he might forget the purpose of adding a
particular note but If there will be a title of note then he will be able to recognize every time
after seeing it the purpose of adding it.
MEMBERS: 14
Applications usually are not using the navigation tab which can give more options to the user
other wise the application will be restricted to only some abilities.
It is noticed that in some notes there is no backend used at all that means whatever the user is
adding in the application, stays in the application. There is no record of the previous data.
OBJECTIVES FOLLOWED:
a) The notes should be sorted from oldest to newest and should be align in in such order so
they can occupy minimum space.
b) There is also one navigation bar and layout bar to interact with us where our contact
details are mentioned and can access the notes.
c) All the notes are stored in cloud storage rather than mobile storage. So syncing of data will
be possible if user lost or broken his mobile phone
d) To do list application will provide the user authentication system which will facilitate the
user to keep his data or notes private. He will be able to sync the data using his login
credentials.
e) There is also some extra functionalities like every individual note should be in float mode
and only take the required area in which we can see the whole list.
f) Colors of the notes should be varying so user can easily find their note and layout should
seen more colorful.
g) The application is adaptive with the size and structure of the notes.
MEMBERS: 15
CHAPTER 3: DESIGN FLOW / PROCESSES
CONCEPT GENERATION
 There are many applications for note taking available on play store but most of them
does not have any authentication system to protect the notes so our main is to built an
application in which only specific user can access his/her notes.
 The second advantage is of privacy. Due to authentication system every User can
maintain the notes of their own separately in the same device. To do this each User
have to login with their credentials and open their account.
 As every note is stored in separate and centralized fire store cloud database so they
are protected from any physical damage to the device and the User can sync and
access the all notes.
 Most of the applications have only space for content but in My Task application, each
node is made up of two columns (title and column). In title column, the User can enter
the title or date of the note so it become easier to find it afterwards.
 All the notes are listed from newest to oldest So it become easier to find and arrange
the notes.
EVALUATION AND SELECTION OF SPECIFICATION / FEATURES
a) The notes should be sorted from oldest to newest and should be align in in such
order so they can occupy minimum space.
b) There is also one navigation bar and layout bar to interact with us where our
contact details are mentioned and can access the notes.
c) All the notes are stored in cloud storage rather than mobile storage. So syncing of
data will be possible if user lost or broken his mobile phone.
d) To access the notes every User must need the login credentials and if the User is
not logged in the User have to create an account.
MEMBERS: 16
e) The application is runnable on all the Android device of config. Higher than kitkat
version.
f) The User can also store notes without logging in. The only difference it will make
that the notes will not be saved and synced.
DESIGN CONSTRAINTS:
REGULATIONS:
 The foremost regulation is that the application should open in minimum time, like to
load the home page of the application the application takes almost 2 seconds and
approx. 5 seconds to log in the account.
 The second need is that, there should be not any limit of words in notes. The user
should be able to add note of any length.
 There should not any limit on notes. The user should be able to able any number of
notes.
ECONOMIC CONSTRAINTS:
Economic constraints are the constraints related to costs and quality of the project.
Our application is generally free. The only money we spend is to buy play console
license, which is of 20 dollar. There are many ways through which you can generate
money from these applications.
a) Crowdfunding
b) Selling special or premium services
c) Advertisements
d) Make the application paid
e) Subscription
We have not choose any method yet because our project is generally like a prototype
and in early access. If the application give good response, we can add these factors
later in the application.
ENVIRONMENT CONSTRAINTS:
MEMBERS: 17
Environment constraints are the necessary condition in the project environment, which
must be followed to perform the functionality. There are some conditions in our
application also:
 As you know, that every note is saved in a firebase cloud storage given below so it
must be necessary that the internet connection of user is ON during adding the notes.
 The second condition is of version of the mobile phone. To run the application the
user’s phone should be of kit-kat version minimum.
The figure of the firebase cloud database is given below:
Figure 1
MANUFACTURABILITY
The constraints in the manufacturing of the an application is considered as the manufacturing

constraints of the project.
 In this app making, java programming language is used which is slower than kotlin.
So, in some case it can slow the performance of the application as compared to the
kotlin language.
MEMBERS: 18
Figure 2
 There are many non-functional features in the application which the user cannot see
but it will increase the quality of the product.
SAFETY CONSTRAINTS
 There are many constraints regarding the safety of the privacy of the user. So it is
important to add a authentication system to login the home page. In our app. , we have
use a google authentication system provided by firebase console. Using this, the User
can login using their google account and sync the notes accordingly. There are many
options for login which are given below:
Figure 3
ANALYSIS AND FEATURE FINALIZATION SUBJECT TO CONSTRAINTS
MEMBERS: 19
 Create a note taking and to-do list mobile application using android development with
many functionalities like taking notes and maintain privacy using authorization
system of firebase utilities and google services. So, every user can login using his/her
account if any, or create a new account. To do list application will provide the user
authentication system which will facilitate the user to keep his data or notes private.
He will be able to sync the data using his login credentials. This kind of application is
also provided in the android mobile phones but does not provide the User
Authentication System to keep the data Private and safe. There is also some extra
functionalities like every individual note should be in float mode and only take the
required area in which we can see the whole list. Colours of the notes should be
varying so user can easily find their note and layout should be seen more colourful.
Apart from those we will upload this application on play store so anyone with android
mobile phone can download this application and use it.
DESIGN FLOW
 Design phase transforms requirement specification into a form suitable for

implementation in same programming language and Data flow is the flow of User
provide information and metadata in the system and environment of the project.
 There are many types of designs and data flow diagram for one project depend on the
approach you have taken. For example this project can be made by using different
SDLC approaches like spiral model, incremental model or prototype model.
A) If we follow the prototype approach to build this note taking application, we have
to first create a prototype of the whole application then evaluate it to get feedback.
After getting the feedback, we have to redevelop the prototype to increase the
quality of the application. We have to repeat this process again and again until we
get the desired result. To follow this prototype model in this note taking
application we have to create an sample application with less functionalities.
The flowchart of the prototype modelling is given below:
MEMBERS: 20
Figure 4
The prototype model has the following characteristics:

1. Limited functional capabilities
2. Low reliability
3. Insufficient performance
B) If we follow the evolutionary approach to build this note taking application, we
have to first create a single functionality of the whole application then test it to get
desired result. If this functionality run successfully then add another functionality
in it. Repeat this process to reach the final application resultant.
This model is also called successive model or incremental model. The lifecycle of
this evolutionary model is given below:
MEMBERS: 21
Figure 5
C) There is also one model called spiral model. This is the best model for the team
because in this model team must decide how to structure the project into phases.
In this model each loop of the spiral represents a phase of the software process:
1. The innermost loop might be concerned with application feasibility.
2. The next loop with system requirement definitions
3. The next one with system design and so on.
In general, there are 4 stages in the spiral model of a project.
1. Determine objectives
2. Identify and resolve risk
3. Develop next level of product
4. Customer Evaluation of Prototype.
We can say that spiral model is a combination of incremental and prototype

model. The model of the spiral model is given below:
MEMBERS: 22
Figure 6
BEST DESIGN SELECTION
The note taking application is an easy to made application but has many components and
functionalities. So the best design model for this application is Evolutionary Model. Because
using this model we can testify every functionality and the modify it to add another
functionality in prior prototype. For example, to build this application we have to open a
blank activity and make the recycle view page to check the layout and positioning of buttons,
the connect the firebase from the application etc.
The stages of Evolutionary model for this My Task Application is given below:
MEMBERS: 23
Figure 7
MEMBERS: 24
IMPLEMENTATION PLAN
To implement the application, every component of the application have two files one java file
and one xml file. Java file contain all the code regarding functionality, class, objects
inheritance etc. and in xml file there is code regarding design, format, size and layout of the
components. You can read these topics in detail in further chapters.
DATA FLOW
The data flow is the flow of information and metadata in the application environment and
system. Like when an user create an account the account is stored in the firestore data
database and when an user login his/her account it can check from this database. For the
notes the there is one cloud storage provided by firebase.
Here in the following diagram given below you can see the flow of data in out Note taking
application:
Figure 8
MEMBERS: 25
Here are some other data flow diagrams for further understanding of the application
working:
Figure 9
Figure 10
MEMBERS: 26
Figure 11
Figure 12
MEMBERS: 27
CHAPTER 4 RESULTS ANALYSIS AND VALIDATION

UI/UX introduction
The application contains different layouts, and for that UI/UX is the very crucial part.
Designing the page is one of the main part of making an application as it is called as the base
of the application. It reflects the frontend which user will see. So , designing a user friendly
design is very important.
Components while creating a UI/UX

UI/UX requires certain requirements while creating application using android studio. We
need to make a different values file for the fonts. We have to create a file for the strings
which are used in the whole application. A separate file has to be made for the images used in
the application. We have to create a file for the colors also. As it is the feature of our
application that it shows notes in different colors everytime while opening the application.
Now, if we come on the layouts of every single file then there are certain parameters which a
developers needs to keep in mind. Which are the constraints, the kind of layouts suitable for
the application view for example, recycler view, list view, constraint layout, match parent and
many more.
Points to remember
The developer has to keep in mind about the color combination while using of the objects
from the palette like button, text view , image view , edit text , icons , list view, card view etc.
The main part comes when a developer constraint the objects in the layout file because a not
perfectly layout file will make the objects not function properly or it make cause the
overlapping of the objects while running it on the emulator or in the person device. There is
one more possibility that the application may get crash.
Some times there is a possibility that the ids of the objects used in the application are
redundant i.e same as that of the id of some other object so it will give the error. Android
studio has made it very easy and it very much developer friendly that it tells about the
possible error occurring while developing the application and it also comes up with a good
solution. While developing a design for the application there are two parts in a .XML file
which are code and design. Every object which developer has inducted in the application has
a code behind it so it gets reflected in the code part but for the beginners and to try with the
UI/UX a developer can easily go with the design part only in which he has to simply drag and
drop the object from the palette and code will be automatically get reflected in the code
section.
Let’s see one by one the main parts of the application which are making the UI/UX of the
application.
Results and analysis
MEMBERS: 28
We will look on some of the codes and the outputs of the code.
CODE:
1. Nav_header.xml
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout
xmlns:android="http://schemas.android.com/apk/res/andro
id"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:orientation="vertical"
android:layout_width="match_parent"
android:layout_height="match_parent">
<androidx.constraintlayout.widget.ConstraintLayout
android:layout_width="match_parent"
android:layout_height="200dp"
android:background="@drawable/cover">
<TextView
android:id="@+id/textView2"
android:layout_width="0dp"
android:layout_height="wrap_content"
android:layout_marginStart="16dp"
android:layout_marginTop="24dp"
android:layout_marginEnd="24dp"
android:fontFamily="@font/abril_fatface"
android:lineSpacingExtra="8sp"
android:text="My Task"
android:textAlignment="viewStart"
android:textColor="#FFFFFF"
android:textSize="36sp"
android:textStyle="bold"
android:typeface="normal"
app:layout_constraintBottom_toBottomOf="parent"
app:layout_constraintEnd_toEndOf="parent"
app:layout_constraintStart_toStartOf="parent"
app:layout_constraintTop_toTopOf="parent"
app:layout_constraintVertical_bias="0.0" />
<TextView
android:id="@+id/textView"
MEMBERS: 29
android:fontFamily="@font/abril_fatface"
android:text="Just Note it! "
android:textAlignment="viewStart"
android:textColor="#FFFFFF"
android:textSize="16sp"
app:layout_constraintTop_toBottomOf="@+id/textView2" />
<TextView
android:id="@+id/userDisplayName"
android:layout_marginTop="24dp"
android:text=""
android:textColor="#512DA8"
app:layout_constraintTop_toBottomOf="@+id/textView" />
<TextView
android:id="@+id/userDisplayEmail"
android:text=""
android:textColor="#1A237E"
app:layout_constraintTop_toBottomOf="@+id/userDisplayNa
me" />
MEMBERS: 30
</androidx.constraintlayout.widget.ConstraintLayout>
</LinearLayout>
Output:
Figure 13
This is the navigation header file which user will see after swiping.
2. Nav_menu.xml file
CODE:
<?xml version="1.0" encoding="utf-8"?>

<menu
xmlns:android="http://schemas.android.com/apk/res/
android">
MEMBERS: 31
<item android:title="General">
<menu>
<item
android:id="@+id/notes"
android:icon="@drawable/ic_event_note_black_24dp"
android:title="Notes" />
<item
android:id="@+id/addNote"
android:icon="@drawable/ic_add_circle_black_24dp"
android:title="Add Note" />
<item
android:id="@+id/sync"
android:icon="@drawable/ic_sync_black_24dp"
android:title="Sync Notes" />
</menu>
</item>
<item android:title="Logout">
<menu>
<item
android:id="@+id/logout"
android:icon="@drawable/ic_vpn_key_black_24dp"
android:title="Logout" />
</menu>
</item>
</menu>
MEMBERS: 32
Output:
Figure 14
It is the menu bar which will appear infront of the user when he will swipe right then these
General and logout section will come.
3. Content_note_details.xml file
Output:
MEMBERS: 33
Figure 15
This is the layout of the content of the note xml file which will facilitate the user to
see his notes and will also allow to edit the note.
As we can see there we are using Constraint layout, in the component tree which
basically allows the developer to simply drag and drop the components from the
palette and we have also used a text view for the display and edit purpose.
4. Login.xml file
Figure 16
It is one of the main part of the application as we are dealing with the privacy
Or the safety of the user’s data. Here the data or the information added by the user
will be connected to the Firebase.
MEMBERS: 34
5. Register_details.xml file
Figure 17
It is for the new user who wants to sync his notes so, he has to swipe left and click on the
sync notes so he will be directed when he will click on REGISTER or create account option.
After that he has to fill in these details and click on sync now.
NOTE: The notes which were created before as an anonymous user will disappear. So, it is
advised that the user first create an account and then start saving the notes
MEMBERS: 35
6. Firebase console
Figure 18
MEMBERS: 36
Here, click on the Authentication to know who has login to the app.
Under the firebase console the information which the user is entering in the
application will be stored in the firebase.
7. Login accounts in Firebase.
Figure 19
Under Authentication the developer who is having the access to the firebase console will
be able to see who has logged in the application.
8. Fetching the data of the user from the firebase.

For data validation
MEMBERS: 37
Figure 20
Under the cloud firestore the users details will be stored.
9. Firebase analytics
Figure 21
MEMBERS: 38
Figure 22
10. Google play console dashboard
Figure 23
This is the dashboard of the google play console from where the developer can see the
application’s progress in terms of users, crashes, countries, size and many more.
MEMBERS: 39
Figure 24
It provides the complete information about the application’s progress.
11.On the play store
Figure 25
MEMBERS: 40
That’s how it looks on the play store from where the user can access it
easily. And the main advantage of the application is that it’s size is less
than 6 MB because in the beginning the application doesn’t have any pre
data so doesn’t occupy much space and then the user can retrieve his data
from anywhere and anytime.
CHAPTER 5 CONCLUSION AND FUTURE WORK
CONCLUSION:
The note taking apps which are available in the android devices now a days are
not providing the sync of the data due to which any person who is having the
device can access the data but by using this app, a user will first sync it’s notes
and then he/she can logout and can login at any devices. It will take care of the
security of the notes.
a) The notes should be sorted from oldest to newest and should be align
in in such order so they can occupy minimum space.
b) There is also one navigation bar and layout bar to interact with us
where our contact details are mentioned and can access the notes.
c) All the notes are stored in cloud storage rather than mobile storage. So
syncing of data will be possible if user lost or broken his mobile
phone.
FUTURE WORK:
Some things which can be done to make the application more compatible and
user friendly. The application can have some different sections like:
i) For study notes.

ii) For minutes of the meeting.
iii) For to do list.
iv) For Shopping.
MEMBERS: 41
v) For Billing.
The application can have a notification bell which will notify at the specified
time to the user about the task which he has assigned to himself. There can be
an accuracy check which will check with how much accuracy a person is
completing his task. The application can have a share and rating option in the
navigation bar. It can also have the priority list in which user can assign the
priority to his task which will organize the tasks more perfectly.
MEMBERS: 42

My Task Final Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

My Task Final Report

Uploaded by

Copyright:

Available Formats

MY TASK – JUST NOTE IT!

TITLE OF THE PROJECT

TEAM LEADER: SHAAN TYAGI (20BCS1023)

in partial fulfilment for the award of the degree of

SOME PERFORMANCE ASPECTS CONSIDERATIONS OF A

TEAM LEADER: SHAAN TYAGI (20BCS1023)

MY TASK- JUST NOTE IT!

Submitted for the project viva-voce examination held on

INTERNAL EXAMINER EXTERNAL EXAMINER

We would like to express our heartiest gratitude to Chandigarh University,

We would like to extend our heartiest gratitude to our project Co-Supervisor

CHAPTERS PAGE NUMBER

CHAPTER 3: DESIGN FLOW/

CHAPTER 4: RESULT ANALYSIS

CHAPTER 5: CONCLUSION AND

1. Table of Contents………………………………………… Page No. 4

SDLC Software development Life Cycle

SRS Software Requirement Specification

NEED FOR THIS APPLICATION

The time taken in building process is approx. 3 to 4 weeks.

Task Time taken in days

Building Home Page 5

Building Navigation Bar 3

Building Layout Bar 6

Building Add Notes Page 7

Building Authentication System 5

ORGANIZATION OF THE REPORT:

Topics you will read in further chapters:

CHAPTER 2 LITERATURE SURVEY

FINDINGS FROM DIFFERENT SIMILAR APPLICATIONS

CHAPTER 3: DESIGN FLOW / PROCESSES

EVALUATION AND SELECTION OF SPECIFICATION / FEATURES

The figure of the firebase cloud database is given below:

The constraints in the manufacturing of the an application is considered as the manufacturing

ANALYSIS AND FEATURE FINALIZATION SUBJECT TO CONSTRAINTS

 Design phase transforms requirement specification into a form suitable for

The flowchart of the prototype modelling is given below:

The prototype model has the following characteristics:

In general, there are 4 stages in the spiral model of a project.

We can say that spiral model is a combination of incremental and prototype

BEST DESIGN SELECTION

CHAPTER 4 RESULTS ANALYSIS AND VALIDATION

Components while creating a UI/UX

Results and analysis

<?xml version="1.0" encoding="utf-8"?>

8. Fetching the data of the user from the firebase.

Under the cloud firestore the users details will be stored.

10. Google play console dashboard

11.On the play store

CHAPTER 5 CONCLUSION AND FUTURE WORK

i) For study notes.

You might also like