I replaced it because of the following:

• It has diffUtil which can compare what's the calculated difference and refreshes only what changed
• It's easy to submit the list as well, there is no need to remember the different methods to update the adapter, just do submitList() and it will do the magic
• It makes the comparison in the background thread as well which makes it even better

For more check out this article - https://medium.com/simform-engineering/listadapter-a-recyclerview-adapter-extension-5359d13bd879

If you're on the home screen and press the back button from the device, the screen turns black and you have to close out before you're able to do anything.

Samsung Galaxy S20 Android 12 latest build

ListAdapter DiffUtil

• checking using oldItem == newItem in areItemsTheSame() is wrong as it would recreate viewHolder if any changes happen
• checking using .id is correct as it wont recreate viewholder for the same item
• checking areContentTheSame() using oldItem == newItem is correct as it will only update the contents of the viewHolder if any details change and not recreate viewHolder

NoteEntity being a class and not data class

• Classes that hold data should be data class
• Data class auto create the equals() method which is need for comparison in diffUtil

Refactored codebase to follow MVVM Arch, which it wasn't following. Used Flows to listen to changes in notes, and state management. This makes the codebase easily testable and maintainable

Worked on the following things:

• Removed the assertion from the production code, its better to use it in testing and not in production/working code
• Enhanced the project structure to be more future-proof and flexible

Feature added

• Splash Screen

Proposed changes

• added SplashScreenActivity.kt to the presentation folder
• added activity_splash_screen.xml layout file to the layout folder
• make the splash screen activity as a Launcher screen

Screenshots

Refactor the CreateNoteFragment.kt and CreateNoteFragment.kt to use view binding instead of kotlin synthetic.

Why have a look here = Android doc and this - Stackoverflow

Worked on the following things -

• Removed the BaseFragment from use because the composition is usually better than inheritance and in bigger projects, this BaseFragment so much becomes huge that it's even hard to read that

• Using the Kotlin delegate getting the fragment instance is easy

• Used the lifecycle scope to launch coroutine in a fragment that is lifecycle aware

Getting this error for the room version 2.3.0 specifically for m1 mac

Caused by: java.lang.Exception: No native library is found for os.name=Mac and os.arch=aarch64. path=/org/sqlite/native/Mac/aarch64

on upgrading the dependency to 2.4.0-alpha04 and above

so basically, fixed an issue with Room’s SQLite native library to support Apple’s M1 chips.

Reference StackOverflow post - Link

Minor changes in spacing, colors and alternative texts, aiming to improve accessibility and reduce warnings. I will soon be making more adjustments to fix all warnings.

Hello @akshatbhuhagal

I was going though this project and noticed that there are some missing items based on the Github Community Standards recommendations that would make the project contributor friendly, e.g. a license, an issue template and a pull request template.

Let me know if this is something you would like to implement on this project.