Base 44 - Overall Feedback

I’ve been with Adalo since the very beginning, and my app was originally built on the platform. It was successful for a long time, but ever since the switch to the 2.0 builder, legacy apps haven’t received much support. Ironically, those older apps actually run faster with little to no lag, while the newer 2.0+ apps are noticeably laggy.

The biggest issue is that this performance directly impacts my users. Any creator knows that poor performance leads to a drop in user retention, fewer sign-ups, and frustrated customers and unfortunately, Adalo’s backend issues are being carried straight into my app.

On top of that, the third-party components I’ve paid for have been a nightmare. Many of them no longer work, and when they break, you’re left waiting months for a fix (if one ever comes). It raises the question: what happens to all the money we’ve invested in these components when they’re no longer supported? I believe there should be refunds or accountability from creators who don’t maintain what we paid for.

To be fair, Adalo’s new CEO has made a lot of great changes. But at this point, Adalo needs to give customers with high-scale apps an option to buy more bandwidth or scaling power. I keep being told my app has “too many items on one page” but if I broke everything down into multiple screens, my users would never use the app. Other platforms, especially those that are fully coded and backed by investors, let users get to their data with fewer clicks and far better performance.

I also encourage Adalo to invest heavily in AI and continue improving overall performance. AI could streamline design, optimize app behavior, and make the platform much more scalable for creators who are building complex apps.

Recently, I found an alternative platform similar to Adalo: Base 44. It costs about the same ($50/month), but it runs much faster, gives you full access to your code and files, and even leverages AI to handle the design (while still letting you customize if you want).

I agree about the need to buy more bandwidth and scaling power. That being said, once you start facing issues with Vibe Coding (and you will), you won’t believe how much you’ll miss Adalo. The chances of reaching real production without writing code in Vibe Coding are close to zero. No-code is possible (of course, with integrations and custom components). I fully agree that Adalo should give users who want more advanced capabilities more options — 100%. But it’s still better than Vibe Coding. Once you dive deep into Vibe Coding, you’ll understand this yourself.

In my opinion, Adalo should focus on continuing to improve performance, offering the option to get stronger servers, and providing much more optimization (there are barely any new components in the marketplace, which is a very big problem). They should also give us many more options — but still in the simple way we have today.

However, to think that Vibe Coding is the solution to everything is a very narrow perspective.

Totally agree. legacy apps feel faster, and the lack of maintained third-party components is tough when we’ve invested in them. What would really help is an option to pay for more bandwidth or server power instead of just “split into more screens.”

I also think Adalo’s edge is its simplicity, so if they keep that while investing in performance, scaling options, and AI-driven optimization, it could support serious production apps without pushing people to look elsewhere.

2 Likes

I agree, splitting screens is just putting on a band-aid instead of addressing the real problem. Many times the need for overloaded screens comes from the lack of components, and you end up stacking workarounds because there isn’t a proper component for what you need.

The ability to have a stronger infrastructure and more components would solve this.

That said, I still believe Adalo is significant, and the direction Jason, James and the team are taking is very positive

1 Like

All–thank you for this thread. We’ve NOT been idle addressing the core concerns raised by @kdy294

In our staging right now we have a code fix that has lowered CPU usage by ~30-40% on a conservative basis. This change alone should significantly improve speed and bandwidth, especially for native apps.

We’re progressing on three fronts and have a company update that is due, suffice to say that we’re making great progress on our own AI-based build. We are taking great care with this, have learnt from the downsides other vibe-coding solutions like Base 44 and will not be messing with Adalo’s simplicity. The AI-guided building will be offered in a way that I don’t think anyone else is doing, but I don’t want to get into spoilers.

All I can say is that we’re moving the needle, we know your concerns, and we’re doing our best. AI has absolutely been a game changer for the velocity we can generate, and every week it gets better. However, we’re still untangling a lot of legacy code and making improvements (such as the big CPU lift) that might not have grand fireworks upon release, but bring us closer to giving you the 3x performance boost we committed to delivering.

I’m extremely happy with the progress we are making, we’re tracking to our promises and I don’t think we’re going to let you down :slight_smile:

2 Likes

Performance and more functionality is the most important thing, keep it up.

Looking forward to hearing about the next update!

1 Like