What are some of the biggest challenges you face when using no-code/low-code tools?
Aditi Jain
18 replies
Replies
Nuno Reis@nuno_ms_reis
Complex tasks, especially around data need to be taken care ourside the platform, because no code is built with a certain use in mind, and if you have to go outside of that build, then you need to actually develop that part yourself.
Usually the tricky part is then connecting the code you wrote with the no code platform, as the options will be limited to what the no code offers you, limiting what you may want to do, and how you do it in your code.
Share
Canonic
@nuno_ms_reis I get it, when I first started using no-code platform 4 years back I was in the same boat, tools would not offer the customizability I require and then just all the hustle to make that no-code tool usable would be so much that I was better off writing the entire code myself, at least now I won't be held back by the limitation of the platform.
Canonic is built to overcome same struggles, where if the platform doesn't have what you need, you should be able to write a custom code that fit your needs, I know the point of no-code tool is to not have write any code but technologically we haven't reached to a point where a tool can build precisely what you need, we are getting there though. Till then I personally believe the only solution out of this where we would have one tool to rule them all is a no code platform that also offers low code capabilities.
Canonic
@nuno_ms_reis Having code optional opportunities really makes it easier to manage data within the tool itself.
That way connecting the data to the front end becomes much simpler..
A full-stack low code platform works on the same principle..
AI Desk by Collov AI
Some of the biggest challenges I face when using no-code/low-code tools include limited customization options, scalability concerns, and potential limitations in integrating with complex systems.
Canonic
@markk0217 What kind of tools have you tried using?
Don't use them any more
Canonic
@alvarovillalb_ What made you stop?
Me.bot
Some of the biggest challenges I face when using no-code/low-code tools include limitations in customization, scalability, and integration with more complex systems.
eventually, some kind of coding or programming knowledge is required to achieve the required objective unfortunately
They are great to get things done easily and quickly, but hardly customizable and scalable. So I would just use them to test out market and from there onward build my app with my own codes
Canonic
@jonathantahiry That’s great.. MVP’s have been one of the biggest use cases of low code platforms.. but I also feel this was the scenario 2 years back, where customisability was limited and users had to finally move out.
Today people have built companies by building products on low code platforms. And some platforms also offer code export which allows the users to have that flexibility of leaving when they like..
@aditijain08 care to share some of the best low-code platforms?
The lack of uniformity between these tools and some are very uninituitive
Canonic
@dikshapatrob I feel the industry is still growing.. if there is too much uniformity in the tools from now, then the problems would also become uniform..
Every tool is trying to make the experience as much easier as possible for its users..
Llanai
You skip the learning curve on deploying robust applications. It's good to build at least one monolith to prevent vendor lock in. I feel more comfortable taking the hard route at least 1x.
interesting reading some of these comment. Although me and my team have built a no-code data analytics platform, I wonder if it holds enough capabilities so that you wouldn't have to customise (that was our aim anyway ha). The platform is made for Tech semi-novices/ SME's though so perhaps it would be enough for their requirements.
Would be great if anyone here could play around with it and feed me your comments on it
I would defo say no-code tools are great to get the base going but from my experience, when certain functionalities get more advanced or need customization - some form of code is needed !
Canonic
@grish_etrnl I agree with you, but I think there are tradeoffs everywhere, I come from coding background and we face same challenges there as well, should we pick a language that is quick to write but is slow to execute or should be pick a language that is fast to execute but slower to write.
Same with hosting infrastructure, should we pick cheaper one which can cause performance bottlenecks or should we pick infrastructure that is very good at scaling but is expensive. To answer your question, I think ideal solution would be no code - low code tool, a tool where you can quickly build something and if you want to customize some part of it according to your use case, you should have be able to do that. This way one can stop jumping from tool to tool to find a perfect tool.
Canonic accommodates this tradeoff, here on frontend you can simply drag and drop components and when you have want to build something that Canonic doesn't have in its library out of the box, you can select Custom component to customize however you want even import external NPM packages. Same is true about backend builder, you can write your own JS functions where ever you think existing webhooks offered by Canonic isn't accommodating you needs.