Articles

Apr 05, 2025

Reading Time: 6min

Why No Code Is A No Go

A cautionary tale in using no code app builders and why they will never work

I still remember it as if it happened yesterday. It was 8pm on a crisp Saturday evening. I was in a co-working call with one of my teammates. Hopped up on caffeinated beverages, we had been working for 12 hours straight. This was the last day of a one week app development sprint.
On the demo call with our marketing partner, I made small talk to delay so we could make last minute updates and tweaks. Then it was my turn to present the fruit of our efforts....
What I demo is a buggy, ugly mess that loaded so slow you'd think you were using dial-up.
This wasn't some revolutionary AI application with complex data analytics. This was as simple as a web-app can get. A basic Create Read Update Delete app (in the biz we call this a CRUD app or database wrapper).
How did this happen?
If you read the title, you know exactly where this is going.

What is a no-code app builder?

For those of you who are new or don't know, there has been an explosion of platforms called low or no code app builders. If you are familiar with a website builder (think Squarespace, Wix, etc), a no-code app builder operates off a similar principle. The promise is that you can build a fully functioning web-app with
  • No programming experience
  • A fraction of the time
  • Pennies compared to hiring a development company
Imagine not having to pay tens of thousands for an app while building it in weeks. Who doesn't want that?

What's the catch?

All no-code app builders have same problems.
If you can build it on a no-code platform anyone can.
Put another way, the types of apps you can build with low/no code solutions have already been done better in other places.
Want to create a forum? Discourse has you covered. Want to fetch and display information from a database for an internal project? Combine Notion with Make or Zapier for something easier and faster than you could do in a no-code app builder without any of the hassle.
The leads into the next reason.
Non-linear difficulty in adding features.
In code, there is a small difference in difficulty between a fetch all query in a database versus a fetch data by user ID.
In an app builder such as Bubble, it could be fairly easy or it could be near impossible. In our failed project with Bubble, we needed to talk to a database and ended up creating a function (in code mind you) on the back-end as a workaround to an inherent flaw in Bubble.
It gets better. Even if you are an expert in one app builder, those skills or functionality don't transfer, and if an update comes out that changes layout or functionality you have to start learning over again.
In addition, a major selling point for users is your app's integration. If using an app builder, you are limited to what they have already integrated.
Unprofitable Pricing Model
In retail business there is a saying,
"In the long run, all value accrues to the landlord."
Instead of renting space in a strip mall, you (the founder) are renting space from the app building platform.
    1. Like retail space, once you set up shop its very costly, risky, and time intensive to change.
    2. If your retail business is successful and it rises the value of that space, the landlord will use this as cause to raise your rent. The more users you gain and the bigger your app becomes, the more you'll get charged by the app builder for hosting space.
This is in contrast to writing your application in code, where all it takes to change hosting providers is re-configuring a few files, and if you really don't like your options you can host on servers you physically own (wouldn't recommend but it is possible).
I won't even mention the security concerns and performance limitations.

Where we went wrong

When the dust settled on the disastrous demo, we did our post sprint breakdown of what happened. We came to the hard conclusion that the only way forward, is to tear everything down, and re-build it right with code as we should have from the beginning.
Two weeks later at the next demo, we blew our marketing partners away. Everything loaded near instantly, the UI was intuitive, and we had more features working than before.
You can check out the full case study here .

Don't repeat our mistake

As alluring as the promises of low-no code solutions are, you (like us) will spend more time, effort, and money then if you did it right from the start.
You can't beat real code with false promises.
Of course I have a bias, so don't take my word for it. If you are curious about low or no code solutions, do some research. Test one out. I think you'll come to the same conclusion as we did.
Using an app builder and want to do it right? Let's chat .
I for one never want to show up to a demo without a product I'm proud of again.
The best way to do that is to do it right from the start.
Think of it like this.
No code is like no bake cookies. It looks like a cookie, smells like a cookie, but as soon as you bite into it you get met with a wave of disappointment and betrayal (not sorry to anyone reading who likes no bake cookies. You need help).
Someone on the team hated his no-code experience so much, he wanted me to post this review (I didn't).
"After spending many grueling hours in the code mines using their cruel platform, I can say with certainty that forsaken software has [redacted] us all. Never in my existence in this mortal flesh have I ever witnessed such a blight upon humanity. May their software remain in the pit until the day of judgement so at least humanity may be spared its infliction upon this world. Their application's UI is sinful at best with how it deceives it's users for claiming to be simple. It is in fact not. If I am to continue using it, I must [redacted] myself and my days ahead of me. A front end, which would normally consume seven hours to create, took FOUR DAYS. Their app's back-end is by far the cruelest sin they've committed. It's very existence has angered my conscripted Desk goblins beyond measure and they seek their pound of flesh for what their app has inflicted upon their minds. I dread that one day the enraged Desk Goblins will rise from the code mines and seek their vengeance upon this pointlessly cruel application. I seek no quarrel with this app’s creators, but they, they lust for blood and vengeance. May the creators of this app find peace upon their minds knowing I have placed the desk goblins in chains and deprived them of nourishment so that the creators of this app may have their absolution be assured. But make no mistake, this is the only time I shall do so. May they never torment another guild with their agonizing app ever again. PS, their back-end [redacted] in the red light district, and their UI for front end design is the worst in the industry of "builder" software. Make it better. Many head pats and hugs,
Desk Goblin Overseer, [redacted]"
Disclaimer: Vasker Tech does not and has never employed desk goblins nor does condone harassment of said desk goblins.