TASQ App

Tasq Purpose

TASQ is designed to provide its users with a digitized to-do list - a list that allows the addition, management, and deletion of tasks that the users
want to keep track of. When it comes to managing tasks, the app emphasizes both agility and simplicity, while also providing users with the option to
customize and edit their tasks more extensively. TASQ provides the users with a convenient user interface that lets an individual view all their tasks
for the current day, week, and even month, with each individual view having its own distinct layout.

Tasq Features

TASQ comes with several features that range over a wide span of categories. First, the application features multiple screens (fragments) - ones
for displaying current data, as well as screens for data creation and modification. Next, a navigation menu which allows the user to easily move
between the different parts of the app. TASQ also comes with database and remote server support for maintaining user logins and keeping track of
the application’s users. Alongside its core features, TASQ supports voice commands for the purpose of task addition and page navigation, as well
as Google Maps for geographically tracking tasks. Finally, the application has sounds incorporated into some of its different parts.

Similar Applications

Microsoft To Do
Do! By Simplerion
Todoist
Google Tasks
Focus To-Do
Tweek
Get it Done
Tick Tick

Summary of app analysis:

In general, we noticed a few deficiencies that similar apps have in common. Those apps are often too complicated in their approach to customizability, making it difficult to create or manage tasks at a fast pace. Some, on the other hand, do not give users the option to customize their tasks enough, which we found to be inconvenient in many cases. TASQ aims to work around those issues, and provide the user with a balance between simplicity and thoroughness when it comes to managing one’s tasks.

Evolution of App:

Checkpoint 1:

For the 1st checkpoint we designed all of the screens for the app in xml and set up proper navigation between all screens. We designed
each screen as a fragment and each screen has a toolbar across the top containing a search icon and a slideout menu as well as a title that
changes based on which page you are on. We also created a slideout menu that slides in from the left side of the screen and displays all page
options to navigate to: Daily, Weekly, Monthly. We also implemented all of our navigation between screens via the slideout menu. When a user
clicks on a view option in the menu, they are then taken to the corresponding screen.

Checkpoint 2:

For this checkpoint, we began the implementation of task addition. At this point, a user was able to access the add/edit fragment from any desired screen,
and add a task to their set of tasks, while also being able to modify some of the fields for a task. We also were able to successfully update the monthly
screen with the addition of a new task.

Checkpoint 3:

For this checkpoint, we accomplished the proper addition of tasks on the Daily screen. We also added more extensive functionality to the monthly screen
to include the display of all tasks for the day the user selects on the calendar. At this point in the project, each individual task on the daily screen can
be modified in terms of its attributes, with the changes being immediately applied and updated when the user hits submit.

Checkpoint 4:

For this checkpoint, we accomplished the proper completion of tasks on the Daily and Monthly screens. We also added task sorting based on the priority assigned
to the tasks by the user. Additionally, we added checkboxes and sounds to each individual task on the daily screen so tasks could now be completed. We also
added database functionality using Firebase and login and registration screens to the application.

Checkpoint 5:

For this checkpoint, we have finished our entire implementation of TASQ. We added basic voice command functionality, which allows the user to trigger voice
commands and ask the app to navigate its menus with voice commands. Additionally, we added Google Maps support to the application, which allows the user to
associate tasks with locations by adding addresses to a task that the user is creating/modifying. Alongside the big implementations, we touched up and fixed
smaller portions of the application to finalize its performance for the current version.

Final Features:

• Login and Registration capability:
  The user is prompted to either login or register when they first open the app. We are using Google Firebase to add users to a database on register and also
  search the database to find user credentials on login. After a successful login or registration, the user is taken to the Daily Screen.
• View Tasks on Daily Screen:
  Users tasks are shown on the daily screen for the current day. Only the description of the task is shown, however, if the user clicks on the task, all of the task
  information will be displayed and able to be edited. Each task has a checkbox that can be checked when the task is completed, if a task is completed, the text
  becomes crossed out.
• View Tasks on Weekly Screen:
  Users tasks are displayed on the weekly screen for the current week (from Monday-Sunday) ordered by day. Like the daily screen, tasks can be clicked on to be edited or
  to display task information and tasks can be completed by checking the checkbox next to it.
• View Tasks on Monthly Screen:
  The monthly screen displays user tasks on a calendar with colored dots corresponding to the “color” of the task. When a user clicks a day, all of the tasks for that day
  are displayed at the bottom of the screen. A user can also choose to view these tasks on the daily screen (day set to clicked day) so that they can be edited. The
  user can scroll through months to see tasks as far in the past and future as they would like.
• View Tasks on Someday Screen:
  When adding a task, a user can choose to not enter a due date, meaning that they just hope to complete the task “someday”. These tasks are displayed on the someday
  screen. On the someday screen, tasks can be clicked on to be displayed and edited and can be checked to be marked as completed. Tasks are ordered by priority.
• Add Tasks:
  The Add Task screen is displayed when a user clicks the “+” button on any screen. On the add task screen, a user can create a task with the following fields: Description,
  Color, Priority, Location, and Due Date. Upon submitting the new task, the task is then added to the users’ list of tasks and can be displayed on its corresponding screens.
• Edit Tasks:
  The Edit Task screen can be viewed by clicking on any task on the Daily, Weekly, or Someday screens. On the edit task page, all of the information about the clicked
  task is displayed and the user has the option to edit any field. The fields they can edit are: Description, Color, Priority, Location, and Due Date. Once the
  changes are submitted, the view for this task on every screen is updated.
• Complete Tasks:
  As explained above, tasks can be completed using the checkboxes associated with each task on every screen (besides monthly). Once a task is completed, it is still
  displayed but its text is crossed out. A user can also uncheck a checked task to mark it as not completed again.
• View Tasks on a Map:
  If a user chooses to input a location associated with a task, these tasks can now be viewed on a Maps page using google maps. The Maps page is centered around
  where the user lives (and is adding tasks) and each task shows up as its own marker.
• Voice Command capability:
  If the user presses the microphone button on any screen, they are then prompted to speak the name of a page that they wish to navigate to (for example, if they want
  to view their daily page they would say “Daily”). The device then listens for input and directs the user to whichever screen they have said.

Current MVC Architecture:

Model:

• AddEditFragment.java:
  The file contains all the functionality for creating a new task. All task attributes are modified or added through this class.
• DailyFragment.java:
  The file contains all the functionality for the daily screen. All individual task fetching and storage, as well as addition are done
  through this class.
• MonthlyFragment.java:
  The file contains all the functionality for the monthly screen. The class creates and stores the calendar, as well as any
  modifications that happen to the screen are done through this file.
• SometimeFragment.java:
  The file contains all the functionality for the ‘Sometime’ screen. The functionality is the same as DailyFragment.java,
  however it contains all tasks without a specific date.
• WeeklyFragment.java:
  The file contains all the functionality for the weekly screen. Any tasks found within the week are managed and modified through this
  class. This class also stores all information for the specific week.
• Task.java:
  The file contains the necessary variables for a single task, which consists of Task Text, Due Date, Color, and a Completed Flag. We will still
  add more functionality to the Task class to cover
• Login.java:
  This file connects to the Firebase “Users” table and processes input from the user to search the database for a corresponding email and password.
  If a match is found, the user is then logged in and directed to the “Daily” screen.
• Registration.java:
  This file connects to the Firebase “Users” table and processes input from the user to add to the database. The user’s email and password is
  saved in the database so that the user can login again. After a successful addition to the database, the user is then logged in and directed to the “Daily” page.
• AddressParser.java:
  Checks the user-inputted address with the GeoCoder and returns an Address
• VoiceCommands.java:
  This java file is called by MainActivity to get the best match between the list generated by the computer for what the user
  might have said via voice input and the list we created of options for the user to say (which is a list of screens to navigate to).

View:

• *ViewModel.java classes:
  All such classes found in their respective folders (associated with a specific screen) are view classes. These classes aid
  the app with screen rotations and general UI support.
• *.xml files in package ‘layout’:
  All files in the layout folder are the general visual layouts for each respective screen. These are the files that are
  displayed visually to the user, thus they are the View portion of our model.

Controller:

• MainActivity.java:
  Currently, this is our controller file. It connects the View files with our Model files, and instantiates the communication between the user
  and the inner workings of the application.

GitHub Repository:

TASQ GitHub

GitHub ReadMe:

Run instructions
1. Download Group5-TASQ-Checkpoint1.apk on the Android device you wish to run the application on
2. Once downloaded, select the file and open it. When prompted, select 'yes'
3. The application will begin installing on your device. Once the installation is complete, select the application, or simply click 'OPEN' on the installation screen.
NOTE:
1. To add a task, the date must be in the following format: MM.DD.YYYY
2. The LOG statements in the code are only used to show that the data is being transferred correctly between screens.

Future Work

By continuing to work on TASQ we could continue to refine the UI and features that we have. One improvement we could make is implementing full task
syncing across devices, expanding on our use of a database. By doing so we could improve the user experience when using the app.