Willem Glasbergen
ย ยทย UX/UI designer and No-code developer

Best practice when using Algolia

Database & APIs

I'm using Algolia with the Firebase extension and defined an API call in Flutterflow. I have a very basic setup with a page that lists all items and a page to edit one of these items.

This all works fine but when a user changes one of the properties of an item in the search results it takes time before the extension picks up the change and the change propagates into Algolia. So when the user returns to the page which lists all items, the change is not shown immediately.

What is best practice in this situation? Should I call the API again after x seconds hoping the changes have been propagated? Or use only the documentID's of the search call and let my list view query the properties of each item? This would however add unnessesary query's towards the db.

I'm not sure what is the best solution here.

What have you tried so far?

I've not found a proper solutions to this problem so far.

Did you check FlutterFlow's Documentation for this topic?
Yes
1