In case others run into this, I just ran into some confusion where results werenāt returning from Algolia, despite following zeroqode/algolia documentation. I realized after some head-banging that you have to have the algolia index name in all lowercase.
ie
dev_IndexName wouldnāt work
but
dev_indexname would work
I think the time has now come for Bubble to offer better search framework - why not recreate something like Algolia for Bubblers? Current implementation is poor and quickly becoming a pain point for us. Does anyone else feel this is the case?
Well, searching through anything more than tens of records slows page loads and seriously degrades user experience. Our app has a calendar (Bubbleās own plugin) that displays appointments. Customers with over 200 appointments a month has to wait several seconds to view them on the plugin. We tried constraining the search to just two weeks before current date and 3 months into the future, but still it takes ages.
Likewise, loading a user list on a dropdown menu to make an appointment hangs for ages when the client list currently contains some 400 records.
I gather searches are done in the browser and that delays every action on the page. App logs donāt suggest there is a need for increase in compute units.
We would appreciate if you can PM me the link to your app, or add support@zeroqode.com to collaborators so we can take a look, @kenlaji.
We have several instances of implementation of this plugin where we are searching trough\loading thousands and tens of thousands of records in seconds, or even miliseconds.
So searching trough 200 records should not be a problem if itās indexed correctly in Algolia and your query does not depend on some other factor, like an un-optimized internal Bubble DB query.
Which means that we should probably improve our documentation for the plugin
Ok that seems an option. I am awaiting Bubble support to get back to me on a couple of things, then I shall be in touch. Meanwhile, can you let me know the process for indexing retrospectively (when there are already records that have not been indexed in the service). Also, the pricing could be better on Algolia!
Bubble should build a functionality like Algolia and make everyone shut up about search for good!
In short - what you need is to run this action on all the items you need to be indexed (and thus - searchable) via Algolia. You can do it in bulk via API Workflow, for instance.
To be sure you got it all - I would just index everything you have, and then add a step to update Algolia index each time you add\change\delete an object within your app logic so that you donāt need to repeat it in bulk once done.
Amen to that
Iām sure they are on this already
Until then - please do index your records, try to see if it works any better for you so that we can all have some nice-working search until Bubble team comes to the rescue
@levon Iām currently using your plugin but I inserted in the admin api key to do updating. My question is, will it reveal the key somehow to the public?
Hey how hard would it be to implement this for a Directory ish type app. I want to create almost like a sub reddit where people can search for users. As well as search for user title that they have posted.