No-Code Web Apps - i.e., Bubble

Hi @Nakkeeran, no problem at all! :) Yes, I’ve definitely experienced this with certain Bubble apps too, and it's something that the Bubble team is actively working on so that speed is comparable to other solutions. For more specifics on speed/performance, this thread has a response from one of the Bubble founders, Josh: https://forum.bubble.is/t/a-fair-and-honest-chat-about-performance/35685/3?u=fayewatson.

The best answer I can personally give is that it really depends on the app’s functionality, and how the app’s data is structured and displayed throughout your app. Those two things can make a huge difference.

For example, a Trello-style project management Bubble app would most likely be fine speed-wise (assuming the functionality is similar to Trello). To ensure the page loads as fast as possible, the app’s data structure should store a list of Boards that pertain to each User’s account, and Bubble would then only load that User’s list of Boards each time they open the app. (This probably sounds abstract if you haven’t seen the Bubble editor’s Data section, but this is what’s referred to as “storing a list of Things” in Bubble, or in this example, “storing a list of Boards”).

That data setup would be significantly faster than the alternative of having Bubble first search through every single Board in the app’s database (this could mean searching through thousands of Boards if you have a lot of Users), and then displaying only the ones that pertain to the Current User. The end result is the same (the Current User sees only the Boards that pertain to them), but searching through the entire database of Boards first, and then bringing back the ones that belong to the Current User, is significantly slower. This setup is referred to as “Do a Search For” in Bubble, and in this example, it would not be necessary and would really slow the app down. (Note: Using "Do a Search For" for is not bad in all cases, it's just not necessary in this example). If you’re new to Bubble and do the intro tutorials, this difference in structuring data is not mentioned though it is important. I would highly recommend getting feedback on your app’s data structure from the Bubble forum before going too ‘deep’ into building an app, to prevent you from having to re-structure data later on after your app is live. The community will gladly share tips and advice!

In contrast, let’s say you have no choice and your app needs to allow users to search through thousands of things (e.g., Products for sale). For Bubble developers that experience this issue, one current alternative is to connect your Bubble app to the external service Algolia. With Algolia, you wouldn't need to query the thousands of Products in Bubble, and Algolia would display the thousands of Products very quickly. Algolia is not good for every single use case, and connecting a Bubble app to Algolia is still relatively new, but there are some examples in the Bubble forum of people exploring this as well: https://forum.bubble.is/t/search-2-0-summarizing-what-ive-learned-exploring-algolia/35631

My apologies for the length of this answer! Please feel free to let me know if anything is unclear or if I can clarify absolutely anything. If you do decide to try it out and run into any trouble at all, feel free to send me a PM in the Bubble Forum (@fayewatson) with questions and I’d be more than happy to help in any way that I can!