AllNotes | Democratizing Notes and Resources | Runtime Evironment library

It should be placed between <> :

AllNotes is null because you have never initialized it, so it throws a NullRef exception when you try to add an item to it

You are nowhere telling the adapter that a new item has been added to the list therefore recycler view does not update. Try doing this,

Let me start off by saying CodeInFlow is a great source to learn from I've used him lots to help build my knowledge, Codelabs are also great and frequently updated by the Android dev team. If you are starting out I would recommend learning Kotlin over java, Kotlin is the future of android and recommend language by the Android Dev Team.

This is how you get a new or existing ViewModel.

You forgot the as const by the second array:

Similarly, I have worked on a project which used Firestore but did not employ the MVVM architecture. In the latter one, the RecyclerView got inflated with data without passing the data to any collection whatsoever.

That's was happening because you were using Firebase-UI library for Android, meaning that all the heavy work was done behind the scenes by this library. What you had to do, is to create only a "FirestoreRecyclerOptions" object, pass it to the adapter, and that's pretty much all of it.

It did not even use LiveData but the changes in Firestore were reflected instantly (which I believe is one of many benefits of Cloud Firestore).

There is no need for any LiveData object, as all the work for getting the data in real-time is accomplished by the library. Yes, Cloud Firestore it's a real-time database, but you can achieve the same behavior also without the use of a library. You can use Cloud Firestore client SDK, but all that mechanism should be implemented by yourself. So that real-time mechanism was actually provided by the Firebase-UI library and not by the Cloud Firestore database itself. To listen for changes in real-time, please check the official documentation regarding, Get real-time updates with Cloud Firestore:

You can listen to a document with the onSnapshot() method. An initial call using the callback you provide creates a document snapshot immediately with the current contents of the single document. Then, each time the contents change, another call updates the document snapshot.

Furthermore,

But now in this project where I want to implement the architecture, I am having an issue with the ViewModel class.

As I understand, you want to implement the MVVM architecture pattern in your project. In this case, you'll have to write code for that, meaning that you should separate the concerns, by creating a Model, a View (activity or fragment), and a ViewModel separately.

And how do I use the FirestoreRecyclerOptions with the ViewModel?

You cannot mix the Firebase-UI library with the MVVM architecture pattern, as none of them is compatible with each other. It's one, or the other.

Or do I need the LiveData at all?

Yes, you need a LiveData object that can be observed in the ViewModel class directly from the activity/fragment class.

The reference docs state that I should use MutableLiveData on some object or collection, and then I should have a method to update the list every time the data changes. There is also an observer method that is implemented.

Yes, that's how MVVM works.

But I don't see any explanation about Firestore or how the FirestoreRecyclerAdapter is even working.

You cannot see any use of "FirestoreRecyclerAdapter" because you cannot use this kind of object in an MVVM architecture pattern. This is happening because when creating a new instance of the "FirestoreRecyclerAdapter" class, you need a "FirestoreRecyclerOptions" object that should be passed to its constructor. This means that this kind of object is tight to the activity/fragment. So if you are using this kind of object in the activity class, you break the MVVM architecture pattern principle, which says that the activity should know nothing about its data source.

What I need is what do I need to implement in the ViewModel class in respect to MutableLiveData on collections from the database and update functions in the FirestoreRecyclerAdapter in the context of Cloud Firestore.

As explained above you cannot do that, with respect to the MVVM architecture pattern. It's one or the other. You can use the Firebase-UI library with all the benefits it comes with, or you can use the MVVM architecture pattern.

You might wonder, which is better?

It depends on what you consider more important, the benefits of the library or the architecture pattern. If you are asking me, I prefer to have a simplified code and use the library.

If you want a simpler code, then you can use Dependency injection with Hilt, and inject an instance of your "FirestoreRecyclerOptions" class, directly into your activity/fragment class.

Please see below one of my repositories, as an example of getting data from Firestore using MVVM:

• https://github.com/alexmamo/SwipeToDelete/tree/master/app/src/main/java/ro/alexmamo/swipetodelete/products

There are two issues with your code:

• You're removing the note class from elements.
• You're not giving elements that should be hidden by default the invisible class.

You need to add the id to the Intent you use to start the Note activity. You do this by using Intent.putExtra(...) and in Note you retrieve it via getIntent().getIntExtra(...)

Solved it myself: TarsosDSP calculates a probability with every note being played. I set my closestNote function to only update the text if the probability is > 0.91 (I found that value to offer "stability" in terms of text not changing after hitting a string and still correctly recognizing the note without hitting the string multiple times/too hard, also tested it with an unplugged, non hollow body electric Guitar)