The App has single activity (MainActivity) and this activity's action bar is used for both the fragments which are inflated inside it. The task is to implement action bar for both fragments and setup a conditional navigation in which an Up Button is showed in the action bar of AddTaskFragment but not in the action bar of AllTasksFragment

The usage of a Up Button is that it should navigate a user back to previous destination of the app he visited but not exit the app https://developer.android.com/guide/navigation/navigation-principles

The styling of Shown Tasks is very basic, improve it by changing the delete icon style, font style etc.

The above image is just an example, the complete UI of the app needs to be revamped, a descent color scheme and UI needs to be implemented uniformly through the app by following Material guidelines

Implement animated transitions for various actions such as

1. When a user clicks on add note/todo button and moves to the next screen where he fills the details of that note/todo.
2. Initially when the user opens the app the already saved notes/todo should have a descent and simple entry animation.

I Would like to set a custom color on the note, to make my cluster notes I select the color on note screen and a piece of that color appears in the list item

if possible, I would like to create this feature

@avidraghav Sir can i improve all fragment recyclerview item layout below is the reference image of improvement like its not exact because screenshot is of another ui but improve in same way.

• In case of a large number of tasks, it is better to fetch data on IO thread rather than the main thread because the app will give ANR Error.
• Hardcoded string converted to a constant in the constant file

Hey @avidraghav , how did you set up automated testing so that whenever someone commits to your code, it runs those tests and generates the report? Could you explain it step by step, or if you have any resources on this? Is there anything else I should know before setting up a CI/CD pipeline?

https://github.com/avidraghav/MyNotes/blob/624946c017a9560b51ac571178ac95eb83500847/app/src/main/java/com/raghav/mynotes/ui/AllTasksVM.kt#L25

Assigning Resource.Loading() to _task variable in the collect lambda does nothing as you are immediately assigning Success to it. Move it outside the scope.

bug keyboar stays over the sanckbar when the user, dont select a deadline

https://user-images.githubusercontent.com/31870695/194767249-4e2c7966-e078-4151-b642-059ab3d28f3d.mp4

Shouldn't we use Parcelable instead of Serializable in our TaskEntity; parceable process is much faster than serializable, I was reading about the difference between them and I found this StackOverFlow

Why is it necessary to provide a dependency for CoroutineDispatcher instances using a DispatchersProvider class, rather than directly inserting the instances into the components that use them?

• You have done this for the centralize management of dispatchers ?
• Can you explain your thought process behind this ?

AppModule

DispatcherProvider