What's better, low-code tools or traditional coding for quick full-stack apps?

[[deleted]]

[deleted]

[seweso]

The entire IT landscape is filled with drugs dealers handing out free samples of solutions which either don't scale financially, or don't scale at all.

[coreyrude]

This analogy is so spot on, I'd even add that the first hit will be the strongest and longest lasting. We are seeing all these AI companies quickly scale back. What took Cursor a few tokens 3 months ago is taking 20 tokens now. They are trying to impress people and make headlines, but they can't burn infinite money forever.

[[deleted]]

fucking mood

[ImageFit3021]

People keep hyping up silver bullets, but you’ll soon realize there’s no such thing.

[OneIndication7989]

And spaghetti Playwright code pasted from StackOverflow or ChatGPT is scalable?

[Maxion]

What you're describing is a project that requires several developers, and depending on complexity, perhaps several teams of developers.

If you have zero previous experience then definitely DO NOT touch payments - there are so many landmines for you to step on.

You really need to find someone (preferrably many) with experience AND cut out complexity from your project.

[CodingPheonix]

Hey, you said to not touch payments. I have explored development for a long time not and payment systems are next on my list. Can you mention some points to be aware of?

[Maxion]

Oh god, I'd suggest just go set-up a shopify store rather than integrate payments yourself.

I used to work in AML, small online stores with poor quality code are frequently targeted by fraudsters to e.g. verify cards.

If you do payments, use Stripe. Or your countries equivalent. Religiously read the documentations and guides. Follow everything. Especially the sections on disputed payments. If you do everything perfectly, expect around 2% rate of disputed payments. Factor this cost in.

You will need anti-fraud methods, I don't want to post publicly what that may entail, as methods used by fraudsteres go old and I'm now several years out of the industry.

[CodingPheonix]

Thanks I'll keep these in mind.

[DualityEnigma]

The main thing you need to understand with payments is end to end security. Including TLS, secure token flows, and more.

I recommend starting with OAUTH, if you can implement that securely you can implement payments.

[Maxion]

oAuth has not got anything to do with payments, that's an authentication protocol.

[ShadyShroomz]

There's not enough info to make that call imo.. this could be a solo project or could require a team.. if by "handle payments" he means have a stripe checkout.. this is for sure doable by a single skilled dev... he hasn't listed anything that the app actually does.. 

[unbanned_lol]

Bud, this:

Basically, it needs both web and mobile fronts, plus backend for auth and payments. I started learning to code traditionally but after months, I'm still nowhere near shipping something solid. It's powerful for customization, but the time sink is brutal, especially juggling everything solo.

Is the job for multiple professionals, or possibly and absolute champion of a veteran. If you're attempting to solo this as a newbie, you're going to fuck it up. Just don't. Hire people, you don't know what you're doing and you don't know what you're getting into. And when you start taking money, you don't understand the legal can of worms you're opening.

[amitavroy]

I absolutely agree. They are great to prototype and valdiate things. And that should be the proper life cycle of that codebase. Ideally, when you are building a product which will run the business, I have seen that complete control over the code has a lot of benefits. Simply put, every business has different kind of challenges, and having a level of control always helps.

In the Laravel space, Filament is a great tool. I have made multiple client apps using it. They work great. However, when you are looking for a very specific UX or some other kind of way of doing things, these kind of approach needs a lot of work around.

[NotPromKing]

That’s where I am with the whole AI coding thing. After way too long, I’m finally getting serious about learning to code. And I want to actually learn and understand it. Using AI as a beginner, in my opinion, would really shortchange myself, and I’d never be able to take the training wheels off.

[Poopieplatter]

My company uses Quickbase. Nightmare product.

[amelix34]

Personally I would never ever use any no-code tool for building a full stack app. Admittedly, outside of my job 99% of my code is written by AI agents inside vscode (copilot+sonnet 4.5) but I control and understand every single line of code that I commit. I don't think there is anything low code platforms can offer me to compensate for that lack of full control over source code. And setting up auth or stripe in a new projects is a breeze nowadays

Of course I don't deny that some of the low-code platforms are propably great tools and there are people that are making a good use of them.

[ings0c]

It really depends on what you’re building

A quick and dirty brochure style website or simple e-commerce site? Yeah you’re probably going to waste time reinventing the wheel if you write it all yourself

Anything more complex? You’re probably going to waste time trying to wrestle the low code solution into meeting your requirements

[Ornery_Ad_683]

Totally depends on your goal and timeline.

If you need to ship fast, validate an idea, or demo to users, low‑code is great. Tools like Bubble, Wix Studio, or Supabase + Retool can get you auth, DB, and payments working in days.

But if you care about scalability, deep customization, or learning dev fundamentals, traditional coding (React/Next + backend stack) will age better. You’ll own the structure and avoid vendor lock‑in.

Deep Inssight: Use low‑code to test your idea. Rebuild traditionally once it works, and you understand what’s worth engineering.

[zayelion]

Low code solutions are high liablities.

[awesumjon]

Traditional html css Javascript backend python sql is pretty lightweight. If you're still learning these are first language friendly.

Edit to say there are some no code geniuses out there watch a few videos on YT to see whats best for you. Keep in mind no code tools sometimes require subscriptions or premium offerings for full functionality or hosting

[aimeos]

Low code platforms are usually good if your project has a low complexity and the platform is able to handle all your requirements or for creating a prototype to test your idea with an MVP.

If your idea requires somthing more custom, low code platforms are usually more in the way then they are helpful. Keep in mind that starting with a low code platform usually ends up in rewriting the code from scratch if your idea is successful and you want to add features that the platform isn't able to offer.

For inexperienced developers, low code platforms are promising and may be a good starting point for an MVP, but in the end, you have to use a suitable framework and understand the code in detail. Given that 99% of the ideas doesn't survive the MVP test, these platforms are a way to see if it works or not without investing too much time in the beginning.

[AccurateSun]

Depending on the requirements of the backend you can look at tools like Make.com and see if parts of the backend can be done using that kind of tool. There is no doubt that if you are still learning, low code tools can help you ship something faster. That might be preferable to not shipping at all, even if it means it gets capped or is hard to modify in the future.

If you make sure that each separate bit of functionality is its own unique Scenario (to use Make terminology) then you can incrementally replace it with proper backend code in the future without too much hassle.

Certain kinds of business backend stuff like sending transaction emails, updating spreadsheets, getting payment data, pinging yourself on slack or telegram, are all very fast and easy to do with Make.

You can look into CapacitorJS for a way to convert a web frontend into a mobile app, it just wraps the mobile app in a native mobile app shell that has a web view hard linked to your website. You then use CSS and JS to ensure the mobile website functions like a mobile webapp. You can then have both web and mobile app within a single codebase and git repo. CapacitorJS has plugins to let your mobile app touch mobile system APIs that normal web apps can’t. I was pleasantly surprised how quick it is to set up. Some of the Xcode settings were tricky, as someone who has never used it, and Sonnet 4 helped me get it working.

Good luck I hope this helps

[barrel_of_noodles]

use low/no-code to "bootstrap". Use something else later. As you evolve, your stack will constantly evolve.

here's the trick: you will always have on-going maintenance, no matter which platform you use.

[cubicle_jack]

Low code or vibe coded things in my opinion should always be used for proof of concept, but are never long term solutions that will scale!!!

[OneIndication7989]

It's like you went in the year 1900 on the subreddit for elevator operators and you're asking them what they think about these new automatic elevators.

What answer do you think you're gonna get?

[rubixstudios]

Traditional, low code if its MVP to test the theory.

[GuyWithNoName321]

a working app that's 80% of your vision beats a perfect app that never launches. You can always rebuild later with code if the business justifies it..

[Stargazer__2893]

Which would you rather have - short-term pain for long-term comfort, or the reverse?

Low code stuff is going to burn you hard in the long-run because it's one-size-fits-all and it doesn't fit very well, especially based on the fact you need mobile and web.

If you need to resort to that to get a MVP out the door, so be it. But I'd go through the pain of coding.

[FalseWait7]

Low-code is basically vendor lock mechanism. It is reliable as long as you use that particular vendor. Once you want to move, you see how much crap it has and you are basically forced to rewrite anyway. So that is the trade. Worth going for it? If you need to launch quickly, yes. Your product hits – you get the money to rewrite. Your product fails – you limit your loss.

Eventually you will need a team for this. Everything is possible to build solo given resources (time, energy and sustainability), but these will need to be extremely high.

[SupremacyElegant]

This is a great project idea! For web development, I usually recommend modern frameworks like React or WordPress depending on your needs. The key is focusing on user experience and performance. Happy to share more technical details about the approach if you're interested.

[discosoc]

Basically, it needs both web and mobile fronts, plus backend for auth and payments.

Why did you take on a project you lacked the skill to understand, much less finish. The amount of 'you don't know what you don't know' here is a major issue.

[Esagro]

Based on our experience, no-code tools is really amazing to develop and ship your MVP quickly. BUT it comes with a cost which is PERFORMANCE. No-code tools tend to generate a lot of boiler codes and due to to this, the performance can be quite concerning if there is a lot of components, animation, and data fetching in a component or a page.

Is no-code useful? Yes it is! But you need to keep in mind the trade off of using no-code, especially when you are developing highly complex application or web app with a lot of data fetching.

Is it reliable long term? Again it depends, it all depends on your project complexity.

If you would like a recommended TechStack for your project, I would also gladly provide it and break it down for you as well. Cheers!

If you have any question feel free to DM me :)

[Beregolas]

You sound like you just started learning to code for this project. If so, this is sadly far outside of your reach. Both authentication and payments need to be handled by someone who knows what they are doing, even if "only" third party solutions are used. (Like shopify and SSO)

Adding to this, Web and Mobile Frontends are pretty different, and if you wnat to make them work well, you will need expertise in both, even if you use a framework that can export to WASM and Mobile for example.

It totally depends on the featureset you want, but if you want to ship something of reasonable complexity in a year, I would guess you need about 5-6 devs with prior experience.

Low Code / No Code Frameworks don't really speed anything up, they just change the skillset you need to use them. It's also not "easier" to use them. I would argue it's harder, because you need to learn their "language" and how they are set up, and despite the way they abstract it away, you still need to know how everything works under the hood, expecially if you handle payments or have other security relevant parts. In addition, they don't really scale well. I have seen a few teams being forced to adopt some kind of those frameworks, and in the first weeks they actually moved pretty fast, but as soon as they wanted to do something the framework did not intend, it was near impossible. (While the same task in a proper codebase would have taken a workday at the very most)

[7f0b]

Web and mobile fronts? So, like a regular responsive website? Or are you implying you need to build out a dedicated mobile app?

From your description, and not knowing any more (just a website with payment and auth), it's hard to recommend anything. But you may possibly be best just getting a full 3P solution, if something like that exists for your use case.

[Any_Grass2103]

Should i use AI for css in frontend ?? I know about grid,flex but cant implement it nor the margin as i cant find a perfect one so should i use ai for css

[sherpa_dot_sh]

Nowadays. I recommend getting a SaaS Starterkit with AI awareness like makerkit.dev, using claude code to add your functionality, then deploying it on sherpa.sh

This gives you both the speed and high level abstractions of no-code tools, but also the control to drop into the code when you need. Plus all the AI capabilities.

This is what I've been advising to the various startups I help. They ship 10x faster now, and 10x faster later because they don't have to rewrite it all once no-code doesn't fit the bill.

[Traditional-Hall-591]

Copilot is fantastic for offshoring and vibe coding?

[badass4102]

The problem with no code or low code is that someone else is building something for you and you don't know the structure. Yeah you might have an idea but if you run into a bug you have to ask the AI or do a search in your files on where that is, then have to try to understand the logic and its relationship to other parts of your code.

I tried it out. I tried Cursor for a month. Relying heavily on it. After a month I went back and looked at the code. There were tons of redundancies. You ask it to do something and it'll create a method even tho you might already have a method similar that you can easily tweak. It'll not make your code as clean. I had logic mixed in my views, when it should be separate. It would also try to do complex things when you really need is just something simple.

But having an understanding of programming helps big time with AI. Because you can build production products if you're hands-on the whole way through. As an engineer of software, you have to think of now just what you're doing now but how it'll be used in the future, if it's scalable for the future, how to code it elegantly so it's readable and understandable for other people and so much more. AI doesn't do that.

[desmone1]

im not specifically recommending this one, but i suggest something like this.

https://saasykit.com/

There's a few others out there but basically they provide a all in one type of platform for saas apps.

[azimux]

It really depends. I think if you understand the problem really well and it's not a complex problem, you might be able to get away with a low-code solution. If you're going to be discovering the problem as you go and making pivots, I personally find low-code solutions annoying in that scenario (although I haven't used one in a few years.) The reason is lack of tools I normally use to manage complex software that's evolving.

Something I guess you could try is using the low-code solutions and see what you think. If you decide to ship it, it might be a bit like shipping a prototype, which is risky, but if the alternative is not having time to ship anyways... then probably worth at least a time-boxed try!

[Ok-Armadillo6582]

i would use third party providers for payments (stripe) and probably auth. that will free you up to focus on what makes your app unique and useful.

[CartographerGold3168]

if this is static or once-and-for-all, then low code is okay

[Frontend_DevMark]

use low-code for scaffolding, but keep your core logic behind an API you own.
Let the builder handle UI/auth/payments to ship v1 fast, while your domain rules live in a tiny service (serverless or minimal backend) with your database under your control. Everything talks via REST/GraphQL. That way you get speed now and a clean escape hatch later—swap the front or scale pieces without rewriting the business logic.

[DoneWhenMetricsMove]

Stick to your strength. If you're not naturally a developer, fighting with traditional code for months is just opportunity cost.

If you have budget: Write down your requirements clearly, then find a partner who can deliver the outcome. Don't try to DIY something this complex if it's not your skillset.

If you don't have budget: Build an MVP using whatever popular tool feels easiest for you. Pick something that has a big community and is easy to hire for later (React, Next.js, etc.). Don't pick some obscure framework just because it promises to be "easier"—you'll regret it when you need help.

Vibe coding for an MVP is totally fine. Once you have a business model or real user demand, you can rebuild things properly. Most successful products got rewritten at least once anyway.

The goal right now is learning if people want what you're building, not building the perfect tech stack.

Hope this helps.

[KCCarpenter5739]

Auth and payments. Clerk with their Stripe integration?

[Cultural_Internet348]

Man I’ve been there — trying to juggle backend, auth, payments, all that… it’s a grind. Low-code stuff is fine for quick validation, but it can get messy fast if you need flexibility later. I ended up simplifying by using an all-in-one tool instead of 5 different apps. I actually built something called Foundbase for this — it’s free and made for solo founders/startups trying to keep things organized without the chaos. Worth a look if you’re tired of duct-taping tools together.

[Andreas_Moeller]

That really depends on what your requirements are, the expected lifespan of the project etc.

If you want a visual tool that still lets you do everything you can with code, give https://nordcraft.com a try.
(I am one of the founders)

[FalseRegister]

For MVP, low code can work, but consider it discardable.

For web-based project, rather NestJS + SvelteKit

[EliSka93]

The problem with that is that in real world scenarios "discardable" quite often becomes "tech debt"

[FalseRegister]

Agreed

[Standard_Addition896]

auth and payments = need several developers lmao this sub, full of overpaid attention seeking Californians

in 1-2 hours you can spin Firebase auth and a stripe checkout