We are paying customers building production-level applications for real clients, not hobby projects. Over the past few days, we’ve encountered a disturbing increase in erratic app behavior, performance degradation, broken logic in buttons, and data inconsistencies across collections. These issues are escalating as we approach a critical launch date—and your status page claims everything is running smoothly.
Let me be very clear: everything is not running smoothly.
After digging deeper, we discovered that Adalo has been silently rolling out new features and changes to the builder. There has been minimal to no communication with your user base about these changes, some of which are significantly disruptive to existing app logic. This lack of transparency is not just inconvenient—it’s unacceptable.
We rely on Adalo to deliver reliable, consistent tools to build client-facing apps. If you’re going to push updates that impact functionality, workflows, or performance, you must communicate these in advance and provide proper changelogs. Quietly pushing breaking changes with no notice erodes trust and puts your most serious users—those who build for clients and pay for this platform—at risk of failure.
We’ve invested time, money, and client trust in Adalo. If this continues, we will have no choice but to consider alternative platforms that treat production builders as first-class citizens and prioritize communication and platform stability.
We urge you to:
Acknowledge the ongoing issues publicly—stop hiding behind an “all systems operational” status when major problems are clearly present.
Improve communication around upcoming changes, releases, and experiments.
Provide real-time changelogs and impact notes so we can adjust builds accordingly.
Stabilize the platform—this is not the time for untested features to be rolled out silently.
You risk losing your core builder community if this continues.
We need updates, I have devs that are sleep deprived trying to figure out what is going on.
Hi David, Thank you for the direct and frank note. I want to start by saying that being responsible for millions of apps that are the dreams & livelihood of tens of thousands is not something we take lightly at all. After hundreds of Maker calls, our duty to give this community stability was made abundantly evident.
Regarding the issues encountered over the past few days, on Thursday we deployed what seemed like an unusually straightforward update to the platform which would have satisfied the #12 most requested feature on our Canny board. It has to do with allowing users to press the enter button instead of clicking on the “Send” or “Enter” icon. As far as recent changes go this seemed to be one of the most trivial and was tested on our build servers before being pushed to production; however, it clearly caused some unexpected issues. Thanks in a large part to feedback like your note and others, we reverted this change earlier today.
You are correct, we have been making a lot of changes to the platform in recent months. The pace of change has been non-stop because there are years of fixes to implement, and our #1 goal has been to ensure that feature requests, stability issues, and performance expectations are fully and completely addressed. In very large part we have been delivering on this promise. Barring the last few days, the Adalo platform has experienced a run of stability over the past two months that it had not seen in literally years prior.
Regarding the request for real-time changelogs, you are absolutely correct and we will be providing them very shortly. Once they are ready we will post here in the forum.
I honestly think many of us would prefer you take a bit more time before releasing a feature—knowing there’s absolutely no chance of critical bugs. Our livelihood depends on your work.
In the case of this specific feature, it undeniably improved search speed—dramatically, I’d even say. But I spent five hours trying to figure out the issue it caused, and if I hadn’t gotten lucky, I wouldn’t have found a solution at all.
In the app business, users don’t show empathy. If something doesn’t work, they leave—and our entire business model depends on that reality.
Let me emphasize again: the “Send” or “Enter” icon feature is excellent!
But it simply can’t be that you’re telling us there’s no issue and making us spend hours trying to convince you otherwise. That’s your responsibility—not ours.
Point well made Nadav. Jason, our CTO, has already changed our testing and release process in response to this very issue.
We’ll be creating a very thorough and integrated test suite for new releases. We were not able to recreate your issues, nor were all other Makers that we were speaking with across the last few days. Of course that doesn’t mean the issue doesn’t exist, just that we recognise we need the testing capabilities across n devices x n OS versions x n network configurations and speeds.