Ada is very good, you guys did an amazing job. My main points for improvement are:
it takes quite a long time to build an app and edit screens. The first app I asked it to do took 46min for the first prompt. Asking it to build/edit collections seems quite fast though.
UI/design of the apps is not my favourite; too many shadows, etc.
something I’ve been saying for a long time: please update the icons, they look outdated
P.S. Many of us have ongoing projects on the Classic Builder, that took many tens of hours to develop, which won’t be possible to replicate with Ada (without many hours invested), so please keep it working well.
Thanks for the feedback! Every piece of feedback is taken into account and helps us improve Ada.
Regarding build times: We’ve seen significantly more demand than we initially expected, and we’re already in the process of scaling up our workers and infrastructure to handle the load. During off-peak hours, some prompts can complete in just seconds or minutes, so there’s definitely room for improvement here.
Regarding design: You can always guide Ada toward your preferred design style, whether that’s specific branding, UI preferences, or design rules. Ada will remember your preferences and apply them as you continue building.
Regarding icons: Ada currently uses React Native icons, but yes, with Ada only we’re planning to introduce more flexibility, including support for SVGs and additional icon libraries.
And finally, Classic Adalo will continue to be supported. We understand how much time and effort many of you have invested in your existing apps.
Thanks again for the kind words and for taking the time to share your thoughts. Keep the feedback coming!
I’m also really curious about one thing! With the Classic Builder, one of the main recommendations for improving performance was to keep the number of components on each screen as low as possible, even simple things like lines and rectangles.
And I’ve definitely noticed a difference when following Adalo X-Ray’s suggestions to simplify screens!
But honestly, it could get pretty frustrating sometimes, because you’d end up having to compromise on the design you originally had in mind just to get better performance.
Do you think this will be different with Ada? Will we be able to build more complex layouts without worrying so much about how many components we have on a screen?
Absolutely! This is actually one of the biggest differences between Classic and Ada.
You have much more freedom to build complex layouts without having to compromise on design just to improve performance.
And the best part is that Ada makes those technical decisions for you! It chooses how to structure and optimize the code based on what you’re trying to build.
Of course, performance still matters, but counting rectangles, lines, or components shouldn’t be something you need to worry about anymore!
I don’t know if this has been answered already, but I’m designing Pour Recall in an Ada app with its own test database. When it’s ready, can I switch that app to share my live Classic database before publishing, so my users, passwords, and purchases carry over? If not, what’s the recommended path?
I been using adalo for a while and let me told you something… Ada is the best thing that ever happen to Adalo … so easy to use !!! Thanks to the team who make this happen !! I do appreciate the job done
I’ve been playing around with Ada a bit, and one thing I’ve noticed is that pretty much everything has to be done through prompts right now. You can manually change things like colors and styling, but when it comes to functionality, even assigning a simple action to a button has to go through AI.
So technically, you could start with a blank screen and build everything block by block, asking Ada to add specific elements and actions. But you’re still relying entirely on Ada understanding exactly what you want. And considering it took about 3 minutes just to create an empty screen, haha, I can imagine that getting pretty time-consuming! I’ve also been waiting for over an hour for it to generate an 8-screen app.. I can definitely see how this could work really well for simpler apps! But I’m trying to imagine building something more complex, with lots of custom logic and conditions, and I feel like it could get pretty tricky. Especially if Ada doesn’t quite understand what you’re asking for, and you have to keep rephrasing your prompts and waiting for each change to be processed.
So I was wondering, are you planning to introduce an option to build screens and assign actions manually, like we can in the Classic Builder?
I feel like having both options would be amazing! Being able to use AI to speed things up, but also having the freedom to jump in and adjust the logic yourself when needed.
Really curious to hear what you guys have planned for this!
If you’ve already created the app, this isn’t possible right now as far as I’m aware. You may need to use the Collections API to retrieve data from your live app to the new app. I’ll also check with the team, to see if this is something that can be implemented and get back to you!
Thank you, Hector! What have you built with Ada so far?
Thank you Helena and Afonso for the feedback! About the prompt completion time, check Jimmy’s response above.
About much more control for manual editing, a few experts have shared similar feedback, but nothing planned yet as far as I’m aware. I’ll check with the team on any updates and get back to you guys next week!
Any other questions? Post them here or create a new new thread.
Here’s why I started with a separate test database and I want to make sure I am seeing this correctly. Since Pour Recall is live on iOS and Google Play with real users if I connected Ada to my live database right away and Ada made a change to a collection or field while I was still designing, my users would feel it immediately in my Classic app, even before I publish anything new??? My plan was to use Ada to get the whole app set up and working first, and then move the real database over. it would be great if there was a way to create a shared copy of the classic database so I could create an Ada app that shares the copy? That would let me rehearse with my real field names and structure without touching my live users.
Ada is really great- amazing actually. And there are some things that I have done within Ada that I don’t think I could have pulled off in the Classic build. So that is exciting.
Right now I am going in circles with Ada on password reset. She keeps telling me that function is not available at the moment??? I have reworded my prompt at least four times and i get the same answer. I am not sure if it is my actual app set up in Ada or if that function is actually not available.
What have you built with Ada so far?