Only 7% of web developers would use low-code/no-code tools to start web applications in 2022
https://flatlogic.com/starting-web-app-in-2022-research
From April to May 2022 we at Flatlogic performed a survey that helped us to understand what are the patterns of starting web apps nowadays.
I've tried to put aside my web dev pride a couple times and go with no code tools, but I always worry I'm going to run into capability limitations at some point. Whether it's authorization, scaling, or cost. But man are they fun to play with.
Same! I recently started playing with Bubble and was really impressed with how quickly you can build a functioning web app.
But the moment I started exploring all the things I would need to support—and the scale at which I would need to support it—I decided to abandon no-code and go fully with React.
I just don't think no-code tools are for "most" builders. They are exceptional tools for those who are starting out for the very first time, however.
Yes, that's a common note on all no-code/low-code tools on the market. Lack of customization and performance issues.
Not an AD :) That's why we at Flatlogic decided to give the source code to devs. Even it is not so good for the business side.
I wouldn't say that all no code/low code tools suffer from lack of customization. Some are very flexible in terms of customization and configurability.
Sure, I don't want to generalize things. But can you give some examples of such tools?
Based on my experience from my clients projects, developers and clients they are not ready to adapt low-code/no-code pricing policies. Also experienced developers they don't adapt no code development model and the learning curve is also important.
Most of my clients user no code to build internal tools that requires fast development and lower support costs.
For sure low code / no code is the future and will continue grow in the next years
Thanks for your opinion. I agree!
When ever I start playing with no-code I feel like I can do the same with code in a similar time frame. To this day I feel if you have a great, adaptable tech stack and some pre-made modules for common tasks you can be up to speed with no-code tools without any of the downsides that come with them.
Sure! Especially when you creating app from scratch!
Hi everyone!
I am one of the authors of this research - if you have any questions, I would be happy to answer them!
My favorite insight is about low-code/no-code preferences: entry-level engineers prefer low-code/no-code more than experienced ones. Another one, quite surprisingly, is a very strong preference for traditional approaches like relational databases and REST API, which makes me think that most of the noise coming from the ecosystem is simply a noise :)
Thanks!
This comment was deleted 3 years ago
Exactly!
That's why we will definitely perform another iteration a year from now to compare the results and understand the dynamics.
The main point for me would be that they suck compared to the speed and control I get when developing web directly. Couple years back, we tried to build a landing page for OrgPad in Webflow. My co-founders spent several days fighting Webflow on a really basic layout. It was also quite expensive.
The resulting output was so bad, that I got angry and rewrote the entire thing into quite plain HTML and CSS (both generated in Clojure, so I could use real programming language). And over the time, we iterated little bit on it, I have created Volcano for static web generation, etc. Recently, we have switched into a new landing page completely build in OrgPad, which is great, so in a way I am building a no-code tool now as well.
Thanks for the opinion!
Yes, that is why the study shows a direct dependence on using no-code with the experience of engineers.
A bit of a contrarian point - I think we're all using no-code/low-code tools to varying degrees. These articles always seem to hinge on whether or not the bulk of a site or app's UI is built with a no code tool like Bubble or Webflow.
Every product I've built has used low-code integrations, and many also use no-code tools. Plugging Calendly into Airtable & Stripe makes for a pretty powerful booking solution, and from there data can be passed into a ton of other tools to get things done.
It's easy to forget how much work products like Calendly and Airtable are doing for you. IMO one of the best things about no code tools is that we've already forgotten how hard it used to be without them.
I personally think that calling Calendly or Stripe as no-code is a bit far-fetched
no code - good for quick to market
do code - good for product differentiation (i.e. competitive moat)
So I guess it depends on your goal
Exactly!
I like to use low-code tools or tools that make coding more fun (+ less tedious). No code builders are often not fun, and I do believe that I can code the thing in similar time frame. Landing pages are an exception.
I use Supabase as my backend, so no more express servers.
Thanks! I personally think the future of no-code/low-code lies in helping engineers to eliminate some boring repetitive stuff, but not a full replacement as the hype says.
Developers have to work with Low Code not because it's easier for them, but because the customer can't afford to pay more.
That might be definitely some of the use cases.
Wow, to me this shows we're still so early. To me, Nocode / low code is the obvious next big thing in web development.
66% of all applications by 2024 will be built using no-code (Forbes)
Hey, thanks for sharing!
66% of all new applications? or legacy too? And how deep low-code will be used in those apps? Continuously or just at the start?
Hey,
It's the new applications and the article doesn't talk about those details.
The devil is in the details :)
Not my apps :)
This comment was deleted 4 years ago
One of the key takeaways seems to be that more experienced devs use no-code/low-code less. Is this because they just don't have as much of a need for it? Or is it because they're wise to its limitations?
I for one, thought about trying no-code and then gave it the axe. Just too much risk of getting knee-deep in it and before realizing that it wasn't going to suffice.
If you're thinking about trying it, though, here's a handy resource that I bookmarked a while back.
I think the reason is that experienced devs exactly know the limitations in customization!
Thanks for the comment!
This comment was deleted 2 years ago
I've always disagreed with how Webflow has positioned their product. They claim to be a no code design tool, when in reality they are a visual frontend tool. Drop a designer into their interface with zero knowledge of basic HTML/CSS/JS and the learning curve is pretty steep.
Yes, for sure Webflow requires some basic knowledge of HTML to make something valuable + pricing is a bit arguable.
I think because WordPress has a way more huge ecosystem of tools and community than Webflow.
As the coding makes easier with visual tools, I think it is arguable :)
This comment was deleted 2 years ago