Adalo's back - and better than ever before. ✨

[astha]

Hi all,

I’m Astha, the new CEO of Adalo. I wanted to write this to introduce myself and answer any questions that the community may have.

Much like James, I’d be indebted to anyone booking time with me directly for a 30 min chat on my calendar here to talk through their experience with Adalo. I’ve already had insightful conversations with some incredible folks from the community, and I can’t wait to hear more. As I say in our team calls: questions, comments, concerns, emotional outbursts - anything goes!

Questions first -

Where’s James? Why the change?

James is very much a part of Adalo as its Chairman (and my boss!). Since Adalo was stable after the acquisition, we decided that it would be best to have a dedicated GM for the organisation, given all the hats he wears. In June 2026, I took over internally - today, just ahead of a huge Adalo launch & rebrand - we make it public.

I know some of you noticed that things went quiet - that was a conscious decision from me, as we were heads down building the new vision of Adalo. This decision gave us invaluable quiet-time to shape what’s coming next, and we’re very confident of our direction. I know it can feel unsettling after all the changes the community has been through - I apologise if it did.

Who am I?

I’ve spent 6+ years in the no-code industry, and with Adalo for 5. You have seen me around - in tickets, in the forum, on our socials or our Slack channel. We know you’ve been around through so many changes and transitions - Adalo 1.0, 2.0, 3.0 and upcoming version - I’ve been around for it too.

I’ve worked closely with the original Adalo team that built our incredible visual canvas, and with James & Jason to bring in rigour in our processes & infrastructure that has made our foundation rock solid. Where we go from here is the best of both worlds, competing in an environment that is shifting at a blinding pace.

How healthy is the company?

Adalo has been, and continues to be, a profitable business - we’re very proud of that. Over the last few months, we’ve invested heavily in the business - both in terms of tech & people - and we wouldn’t have done that if we weren’t confident in its future.

Where does Adalo stand in 2026?

I’ve outlined the vision for the new Adalo in a blog here.

Are we abandoning our roots & our OGs?

Not at all - we’re building a business and so are you. How would we feel if our software providers shut their offering down, leaving us blindsided? We refuse to do that. Our visual builder continues to be supported, and its stability is a focus for us. We also don’t think we’d be pushing anyone to the new version of Adalo - it is truly that much more powerful, that you’d think of switching on your own, in due time.

As for the OGs, our support to both the makers and the community has been top of mind. We’ve had longstanding conversations with Experts on our Slack channels and have been trying to create a landscape where our wins translate into larger wins for the Adalo community. More on that post-launch.

Meet the Team

I also wanted to take a moment to introduce the Adalo team; some old & new faces.

Jimmy Noujaim is our new CTO - he’s also been around for years, contributing to the Adalo ecosystem, and we’re so lucky to have him lead tech for Adalo going forward. The choice was a true no-brainer! Jimmy, Daniel along with the rest of our team of brilliant engineers are the tech prowess behind the new Adalo.

Gabrial, Dilon and Kyle are names you’d see on our social media and outreach efforts, as well as products like the Adalo Studio. You’ve spoken to most of these names before - and they’re rockstars. Jessi, Jahnavi, Shipra and Vagisha are your trusted touch-points for anything Adalo. Everything from support, to resources and reaching out to our makers to help them be the most successful version of their apps - they’re a differentiator for us as we continue to be the platform you rely on.

Honestly, I feel extremely lucky to get the chance to lead this incredible company with some amazing people. With the job comes tough decisions, but so many opportunities to give back to the community. I hope I can prove myself and the team worthy of the trust you continue to place in us.

We hope you will give us your valuable feedback so that we can continue to improve the product and processes with transparency and accountability. I look forward to hearing from everyone - the good, the bad and the ugly.

[afonso]

Best of luck Astha! Excited to see what’s coming!

[Kaycee]

Congratulations

[IFIOgirl]

Congratulations, Astha! As a first time, no-code builder who launched Pour Recall at 61 with no coding background, I can honestly say Adalo’s support system is the reason I didn’t give up. The forum, the team, and this community have answered my questions at every step. Adalo’s success is our success.

[deepvyas]

Congratulations @astha

[SynopsisLabs]

Hello @astha,

Wishing you the best in your new role.

I have been experimenting with Adalo for several apps I am developing and keep stumbling over the same hurdle. Coming from the world of traditional programming, starting with MS BASIC back in the 1980s and progressing through various programming languages to today’s no-code and low-code app builders, I find one omission in Adalo particularly difficult to understand: the lack of native variables for storing and manipulating data.

In traditional programming, variables are fundamental; whether storing text, integers, dates and times, boolean values, or arrays. Developers use variables to hold temporary data, perform calculations, manage application state, and pass information between different parts of an application.

I struggle to understand why a modern app builder does not provide this basic capability natively.

I came across this forum thread from 2020, in which app-level and screen-level variables were suggested as a feature to be added to the roadmap. Given how fundamental this functionality is to application development, I would be interested to know whether there has been any progress on this request.

Several workarounds have been suggested, but none seems like a satisfactory replacement for native variables:

• Creating a collection to store variable names and values: This raises questions about data types. How would the value field handle text, numbers, dates, boolean values, and other data types appropriately? It also introduces additional complexity for something that should be relatively straightforward.

• Creating an unlinked screen containing numerous input fields: Using input components to hold temporary values feels like an awkward workaround rather than a proper solution. It adds unnecessary complexity to the app’s structure and makes the application harder to maintain.

I appreciate that no-code platforms have their own design approach and constraints. However, native variables, with appropriate data types and app-level or screen-level scope, would make Adalo considerably more flexible and intuitive for developers who need to manage temporary data and application state.

I would like to ask the Adalo team to consider this feature a priority. If there is insufficient feedback to establish demand, perhaps a community poll could help determine how many existing users and prospective users would benefit from this functionality.

I would also welcome feedback from the Adalo team on whether this capability is planned and, if so, whether there is an anticipated timeframe for its introduction.

I believe this would be a meaningful improvement to the platform and would eliminate the need for many of the workarounds currently being suggested.

Thanks

Steve

[Eugen]

Hi Steve, in case you missed that, I built several components on Adalo and apps using React Native Async Storage (local storage) to store data physically on the device instead of on database. So even without being connected to internet, your app, or parts of it, will still work. If they will implement it as native thing inside adalo, will be super.