offer a couple / few styles, that could be organized in style families. ( like font families)
So, my “Share” icon matches the style of my “Profile” icon… etc.
Generally speaking, I like to build with smaller components, to build custom.
ZOOMING-out.
I could make better designs, with better controls.
If tools like snapping, guides, 3-5 selectable layers, and style sheets (much like adalo has for fonts, now), a lot of time could be saved.
Between actions, database, and design. I spend a disproportionate amount of time tweaking designs. Adalo has too much of a non-standard “order of operations” to design productively. i.e. resize text while it is in a rectangle VS resize text BEFORE it is placed in a rectangle.
HATS-off to the team at Adalo. Just making all this stuff work together is amazing.
Would you be able to create a seperate topic for this in the Roadmap > Feature Requests category? (first proceed with a search because then you can simply add a reply with your vote and those topics are prioritized in the search results) If you’re facing any issues related to this component or would love to see any improvements in the component, please post them here!
I am picking up, what you’re putting down. Much respect. However, my Spidey senses tell me, adding features to their to-do list isn’t beneficial. I am paying Adalo. Think about it.
I am old, and old school. Quick story / reference: Websites used to have a single blue hyperlink, in which users COULD give feedback, and developers were over-the-top enthusiastic about getting feed back ( Much like Adalo’s CEO, THANKS GOODNESS!! clap clap ) Now-a-days, or Previously, complete opposite. Not fan. But, I understand that the internet will always belong to the future.
Thanks for sharing your opinion, @C3PO and I completely understand it!
Adding a feature request actually helps a lot because once more makers vote on the same idea, it becomes much easier to prioritize. I remember James (Adalo CEO) mentioned this under in one of your topic recently that the engineering team’s main focus this year is AI Ada, while a smaller group is working on new components and smaller requests.
While migrating the Canny data into the forum, I noticed many requests that were completed but never updated with the solution as well as some commonly requested features that still aren’t available like some of the ones you mentioned above. I’m currently reviewing everything one by one, merging related requests and sharing those with the team, so requests stay visible and tracked! I’m reading every topic and reply so your thoughts and feedback are definitely being noted! Hopefully eng-team be able to ship more of these basic improvements this year and with the help of AI, move a bit faster too!
If you’re open to it, creating a feature request topic and adding your vote really helps. Separate topics for each feature (with sketches or examples if possible) make it easier for us to understand and for others to vote but if you prefer combining them, that’s totally fine as well.
Thanks again for taking the time to share your ideas, have a great day!
@Santiago, I’ve shared this with Michael and he mentioned it should be an easy add which he would have an update this week! Also he mentioned, around 4 more new components will probably be available this week, so stay tuned!!
Just to give an update here! 3 components got released last Wednesday (you may have noticed) but due to a reason, they got delisted on the same day. They will be back again very soon and they were,
@diegozane, yes, for the value it would be the deep link (URL format) with the ID from magic text and upon scanning the generated qr code, it will open that URL. (I didn’t had much time to test and play with those though as it got delisted )
).
).
Features at a Glance
).
Components Configuration
Recommended Use Cases
Learn More
Try It Live
We’d love your feedback!
