Isuue with messages stram about flutter_firebase_chat_core HOT 6 CLOSED

Friend you did an excellent job!
If you were in Israel, we would hire you, definitely.

from flutter_firebase_chat_core.

Yeah, this was done to fetch all messages, I though Firebase libs were smart enough to do the optimisations later. We will need to split between the load and update otherwise?

from flutter_firebase_chat_core.

In my implementation, I first of all get all the messages currently on firestore and then listens to the updates:
Check this stackoverflow question I have asked

from flutter_firebase_chat_core.

Yeah, but this is like for the last added element. What about history or updates?

from flutter_firebase_chat_core.

Well, on my implementation I first off all get all the messages and then the stream listens to updates, use "updatedAt" instead of createdAt to get updated messages. For deleted - I don't have a solution

from flutter_firebase_chat_core.

Yeah, forgot about deleted ones.. So basically this was done as a proof of concept of the chat and planned as something that will work (and I need all updates so it works). Never planned further optimisations, because making and describing to different people and different use cases how it works - it does not make sense. Every case will be unique and there will never be a perfect library. So I think it should at least work as intended - as an early stage proof of concept, where you can show a working chat to your client and save some money on an initial implementation and then do a complete solution when client has more money to spend :)

from flutter_firebase_chat_core.