New release! Adalo 3.0 is here!

Adalo 3.0 is here! Republish your apps for a 50->100+% speed lift!

After (just over) a year of working hard to deliver Adalo 3.0 (Adalo at 3x the speed) we’re delighted to announce an update that will drop current CPU usage on average by 40-70% on your current app**.** That means you should see a 50->100+% doubling in speed, assuming you’re up to date with our other improvements! If you haven’t republished your apps from before August 2024, your speed will be over 3x, especially so with a native app!

Here’s a quick side-by-side CPU comparison between the most recent version of Adalo and the latest version (if you republish). Below we’re showing what many of you have asked us to address: list loading speed!

	**Before:						             After:**

combined (1)

Left is the previous version. Right is the latest version. Both simulations are run on Playwright, so the actions in the simulation are identical. Note that on the left, CPU load goes >100% because the app loading requires more bandwidth than the simulation was allocated. On the right CPU rarely gets above 50%, or if it does it drastically drops.

It isn’t just list loading, but the CPU costs to load any screen. Below we have a screen with an image and a list. While both are pretty fast, note the difference in CPU requirement. The black screen on the left was the most recent version of Adalo. The white on the right is the newer version (if you republish). To load the same screen, there is an entire spike of 103% of CPU that is removed by the latest infrastructure.

Adalo App Speed - Side by side (4)

While most of the improvements in this latest version will automatically be applied when you republish, the React Native improvements require a toggle (especially as it may introduce bugs with some marketplace components that their developers have yet to update.) To activate the new architecture, please go to settings in your builder and scroll down to the React Native section and ensure the toggle is set to on:

Adalo 3.0 Status - Delivered :package:

:white_check_mark: Switchover infrastructure for stability, scalability and greater control

:white_check_mark: Overhaul and optimize 176 backend services

:white_check_mark: Optimize caching, especially around images and rendering to increase app speed

:white_check_mark: Provide automatic database indexing to reduce long-running database queries - ensuring fast responses with larger record sets.

:white_check_mark: Provide X-Ray–an AI tool to review builder layouts and audit potential known performance issues

:white_check_mark: Simplify the Adalo Builder codebase - removing unnecessary code and dependencies to increase speed and reduce bugs. This step has led to our CPU / speed improvements in this announcement.

:white_check_mark: React Native upgrade - phased roll out is underway (after 3 5 months of testing!)

:white_check_mark: Adalo’s code refactoring - re-writing what gets pulled into a default app and rewriting this to pull in only what your app utilises.

Having met our performance goals, we still have more work to do. We’re confident there are more speed and CPU gains we can deliver over the next 3 months to increase speed significantly.

Bring Your Own Database to Adalo!

Our CTO, Jason, did a walkthrough of how you can bring (pretty much any) datasource to Adalo. Here it is!

What about AI?

Yes, we’re on it! In our dev workshop, we’ve been busy creating what we think is a unique approach to AI building and one that we believe will make everyone very happy. We don’t want to give too many spoilers away here, but we’re going to kill three birds with one stone and deliver on multiple requests from our Makers.

We’ve been watching what other No Code and Vibe Coding platforms have been doing with AI, and see the struggles as well as the benefits. Our approach will keep the human in control and let you guide every step, should you so choose. Importantly, we’re keeping 3 things top of mind:

  1. The resounding message from Makers is that Adalo’s builder is the simplest and easiest canvas that exists, so don’t ruin it! We’re holding this simplicity as sacred and ensuring it won’t be lost with an AI roll out.

  2. AI can make wondrous things, but at the end of the day what you are making needs to conform to your vision. As such, the ‘last mile’ of creation needs to be human. That is, you must be easily able to follow along with what the AI has built and be able to easily change anything to make it resemble what you need. Prompting to get the final things perfect isn’t (currently) proving to be a great experience.

  3. AI creation can lead to ‘sharding’ - where reversions in its development can introduce incomplete patching and ultimately lead to something that breaks. We have a solution to that.

We’re really excited with where our alpha builds have gotten to using AI. We hope to be able to open up a beta to the Friends of Adalo soon! I get in trouble for setting dates, but my desire is to get this to the public before the end of the year.

Security

2FA Security

2FA was rolled out a couple of months ago, but in today’s world security deserves its own section. We can’t emphasise enough that everyone should have 2FA turned on for every service they can. This is available to all Makers.

To enable 2FA, login to your Adalo account and go to Settings. At the bottom of the screen you’ll see this:

After clicking the setup button you’ll be presented with a short list of instructions:

Once completed, 2FA will be enabled and your Adalo account will enjoy an additional layer of protection.

Please turn this on.

Other Features

AI-powered Chat

We continue to test and refine AI-based chat support to ensure you can obtain answers to your questions as quickly as possible. You can access AI chat by clicking on the question mark icon located at the bottom right of the app builder and clicking Adalo AI Chat Bot.

App Orientation Options

It’s now possible to set the desired app orientation. To change it from the default of both portrait and landscape, go to your App Settings panel and change the App Orientation setting:

Improved Scheduled Notification UX

We’ve improved many aspects of scheduled notification creation and management, designating which settings are required and which are optional, and improved input requirements for the scheduled date field.

Improved error handling for CSV imports

Uploading CSV data into Collections can sometimes be a confusing process, and so we’ve improved error handling in order to more effectively guide Makers when things go wrong.

Increased the Collections Display Modal Viewport

Now it’s easier to see more data when opening a Collections display table.

Lazy Loading for Social Media Lists

We’ve added lazy loading for the social media lists. This enhancement ensures faster loading times and a smoother experience when browsing through extensive lists of social media content.

Improved Date/Time Filtering

We identified and resolved a bug associated with filtering on dates and times which consistently spiked CPU and hurt performance. Profiling the app CPU and memory consumption both before and after the fix showed a dramatic improvement to performance.

Upgraded the Preview and Runtime Environments

The primary outcome here is a general performance, stability, and security improvement to how apps load in the previewer and how they generally execute regardless of target platform (iOS, Android, Web).

Infrastructure Updates

Running a service as complicated and popular as Adalo involves a constant drumbeat of background activity that, while critical, is unlikely to be noticed by Makers unless we tell them about it. So although it’s likely TMI we’ll recap it anyway just for completeness sake.

Smaller App Bundles

We’ve also poured a lot of effort into reducing the size of app bundle sizes through smarter dependency inclusion during the app packaging stage. Some of this work is already in production and has reduced app bundle sizes by several percentage points. This brings many benefits, including faster installation times, faster load times, and reduced deinstallations due to storage concerns on older devices.

Migrated Android build Infrastructure

This migration was one of the very last pieces of the puzzle regarding our almost year long move to faster and more stable infrastructure.

Removed Remaining App Action Overage Code

Although we disabled app action billing overages months ago, some of the code used to manage it had been hanging around inside the code base, so in an ongoing effort to simplify and streamline Adalo everywhere and anywhere, we’ve removed that logic. Bad ideas be gone!

And then??

We’re working towards:

  1. AI building. With Adalo 3.0 delivered, this becomes our main effort.

  2. Google SSO

  3. Adalo Function Hub. A way to access API endpoints to manipulate numbers, strings, dates, times and more - but without relying on an external tool like Zapier or Make. Still in early stages of development.

  4. Adalo Experts Retest & Retraining. We’ve received most of our app submissions from Experts, and we’ll be creating retraining to better align our community to how Adalo can create performant applications. There will also be a number of Experts removed from our listings.

  5. Revamping our Google Sheets connection. Makers want to use Google Sheets as a collection in their apps, and so we’ve (almost) completely rebuilt the connection to serve as a database for you.

  6. Super secret project - still remaining a secret for now! :smiling_face_with_sunglasses:

With Adalo 3.0 rolling out, we’re excited to turn to a new chapter, but a lot has happened since I personally talked with many of you. I’d love to reconnect and hear about what you’re building (and what you’re not building) + how Adalo can better support you. So please find some time on my calendar! We’ve a lot of dev bandwidth that is now freeing up after the yuge overhaul, so we want to ensure we’re aligned to what you all need!

:heart:
James & the Adalo team

17 Likes

Amazing work, James - nothing is more important than speed.

After the upgrade, is the performance of the PWA and the native version identical?

The Function Hub is critical, and I’m very glad to see it on the roadmap.

Thank you so much!

1 Like

Hey @nadavma2 PWAs will be much faster under the new architecture, but list performance on native apps got a big overhaul that should cure many performance related issues. Edit - both PWAs and native apps will be faster, but native apps benefit from a big list-based improvement as well.

1 Like

Long time listener, first time caller here!

Great news hearing about all the continual and major improvements.

My app is still in the legacy builder. Tests with Android native were beyond discouraging, so I put my product launch on hold to seriously re-evaluate options (such as starting over in another platform). But, I keep hoping a new rollout will save me.

With that said - Are legacy apps gaining any benefit from this latest 3.0 rollout?

1 Like

This is great news James!!

Let me know if you guys need help testing out the AI building :slight_smile:

3 Likes

Hey Samrocks–unfortunately not for the legacy platform (Adalo 1.0).

The responsive architecture, allowing you to push a single version across any device, is what we’re developing and improving. I know a lot of people are fearful of moving off the legacy build, so maybe you can wait to give your legacy build apps to our AI builder when it comes out?

1 Like

Sounds good - I just have two comments:
1. There are missing components. The marketplace is very outdated, and it’s essential to add new elements there.
2. The Adalo Function Hub is critical - I have a large number of simple processes running in Make, and this feature could easily solve that.
3. The lists and search engine need a major upgrade. Many users, including myself, rely on custom lists only because the default ones are not powerful or flexible enough - we have no choice. As a result, we’re forced to use custom lists that hurt performance (and even those are sometimes insufficient, since for example there’s no way to control the display order).

Thank you!

3 Likes

Thanks for your feedback! We’re very aware of 1. and have a plan.

  1. is being delivered.
  2. Yes. Do you have an idea of what you would like to see?
1 Like

It can display the list based on multiple layered criteria — for example, first showing all items that meet criterion A, then filtering those by criterion B, and so on.

Currently, it only supports sorting or filtering by a single criterion, which means that achieving more advanced filtering logic would require at least a dual-list setup.

Regarding the search engine — it should be able to trigger actions during the search process (for example, if no match is found, perform X), support “fuzzy search”, and include the option to integrate AI-based search capabilities.

Multi-filtering - absolutely!

Search - makes sense.

Lists - okay, thanks for that feedback. Let me rev something with the team and reach back out!

3 Likes

I wasn’t fearful. I converted it to 2.0 and many layouts broke, mostly related to conditional visibility with things no longer automatically moving accordingly. Redoing complex layouts seemed like a major time investment.

But I may take another stab at it!

3 Likes

Was delighted to talk to @nadavma2 today and hear his speed has improved :heart:

1 Like

Thank you very much, James. It’s been a pleasure.

I’ve attached my comments in the email, and I hope they’ll be implemented soon for the benefit of the entire community.

Hi @james.crennan Crescente from Shifty (staffing mktplce in Spain).

Im loving the new Adalo 3.0 version, however when I try to update some of my apps to that version, it says that some components are not yet available in react native (from NoCodeMonkey).

Any news on when will everything be compatible and tested to work with Adalo 3.0? I’ve been waiting a long time for this and im only this little issue away from it.

Hey @Crescente thanks for writing in! Our 3rd party components have been very slow to update, and we fully recognise this is a pain for you and the others using our 3rd party components. With many more updates coming, this creates a liability for us at Adalo being able to get everyone’s apps improving as fast as we like.

We’re going to take steps to give you what you need, especially if the 3rd party component marketplace is letting you down. Can you tell me which components you need?

James

1 Like

Bravo! @james.crennan Adalo needs to put hands on it.

Hey @Crescente, thanks for the update on your component issue. We’ve updated the component you mentioned when you messaged us so it’s compatible with Adalo 3.0 and it should be live now in the marketplace.

We have been slow with regards to this specific update and were too slow to make internal changes to adjust. Fortunately, our new dev team has been able to fix things quicker and we should be able to respond much quicker to updates going forward with this new team.

We know this is important and we should have most of the components submitted to Adalo by the end of next week at the current pace.

If you have any questions about specific components, you can message me at matt@nocodemonkey.io.

1 Like

Hey, thanks a lot for the components you’re building for the community — it’s really valuable.

I think many of us would benefit from custom lists with advanced filtering/advanced search capabilities.
This is something that’s currently missing for a lot of app types in Adalo.

I’m available via DM if you’d like to dive deeper

1 Like

Hi James! Thanks for the reply! Yes, now its working and the app is going considerably faster, which is a big win and will keep us in Adalo for a bit longer.

Using my moment of glory, this 3 little details would have improve my onboarding experiencie + development speet by a lot:

  1. When selecting a property from my external collection, its incredible painfull to find the correct property, specially when databases get bigger. For context, I have some Airtable bases with 400+ properties, and in order to just select one I need to go to the data collection, open the external collection, find the property and move it manually to the top. Otherwise is impossible to find. Just by adding a “search” in the list of properties (like you did with pages) would save me a significant amount of time.
  2. When I first started using Adalo, I almost stopped because of how frustrating it is to write in the “Text” space of components. It goes crazy and totally unpredictable. To show you how much of a pain it is, I always use Adalo with a google doc open next to it, just to write the text and then paste it.
  3. When you update an external collection, if enough records have a certain property empty, Adalo stops reading that property. This has caused my app to crush multiple times.

Thanks for everyhting! Love Adalo, and I think your value prop is super clear

Agree with @nadavma2 on his points! TBH, I think Adalo wouldnt be a fit for me withouth some of your components - like marking calendar - that for me is key.

Also @NoCodeMonkey i’ve been talking with your support team! They actually helped me on their side, so good. Now I uploaded the newest 3.0 version and it works! However, I would recommend to update the “Last updated date” of the component in the marketplace. It still says “A year ago” and it scares me a bit.

Pro tip: There are many components that I havnt bought because I didnt really know if you were still around, as most of the info related to you is old - 2022 or so. I would strongly suggest some kind of banner or something in your website with the latest product updates, so I know that you are not out of the picture.