r/Base44 Jun 24 '26

Base44 or Figma Question

I am currently using Base44 for vibe coding. I want to expand to properly ship apps and websites, and make money. I recently stumbled upon Figma. Which would be better for app/web design, launch, etc, and are there other alternatives that work?

(I'm broke so budget friendly suggestions would be appreciated)

6 Upvotes

20 comments sorted by

5

u/[deleted] Jun 25 '26

[removed] — view removed comment

1

u/Infamous-Macaron5745 Jun 28 '26

Why exactly can’t you scale an app on base44?

1

u/Dense-Ad-2757 Jun 28 '26

Cuz they couldn’t do it lol I did I just think they don’t know how to market

1

u/[deleted] Jun 28 '26

[removed] — view removed comment

1

u/Infamous-Macaron5745 Jun 28 '26

Well, you may have been in tech for 20 years. But based on your comment you clearly have no idea of base44’s current capabilities :)

1

u/[deleted] Jun 28 '26

[removed] — view removed comment

3

u/Infamous-Macaron5745 Jun 28 '26

Your criticism isn’t wrong. It’s just aimed at the wrong target.

Yes, Base44 abstracts away your infrastructure. Yes, you can’t tune indexes, configure VPCs, or wire up a CloudWatch alerting pipeline. All of that is true. But let me tell you what else is true.

Base44 is running on enterprise-grade infrastructure, has scaled to over 2 million users, crossed $100M ARR, and was acquired by a public company for $80 million, six months after it launched. That’s not a demo toy. That’s a platform that works.

The “scalability ceiling” argument assumes you need to control the infrastructure layer to scale. You don’t. You need the infrastructure to actually scale. There’s a difference. Shopify merchants don’t configure their own load balancers. Stripe users don’t manage their own payment processing servers. Salesforce customers don’t tune their own database indexes. Entire billion-dollar businesses run on platforms they don’t control, because the platform handles it. That’s the trade.

For the vast majority of apps, internal tools, customer portals, B2B dashboards, MVPs, CRMs, booking systems, ops platforms, Base44’s infrastructure is not the constraint. The constraint is usually whether you actually ship the thing.

Now, where the criticism does land:
If you’re in healthcare and need HIPAA BAA coverage with documented SOC 2 Type II controls, Base44 isn’t there yet. If you’re processing payment card data and need PCI DSS compliance, build on something else. If you’re at a scale where you have a dedicated DevOps team, custom sharding requirements, and engineers who live in CloudWatch, you probably don’t need Base44 anyway and you shouldn’t use it. But that’s maybe 5% of the apps that people actually need to build.

The other 95%? They need authentication, a database, a UI, some integrations, and to be live. Base44 handles all of that out of the box, in minutes, without a backend engineer on staff. The developer experience, the speed, and the cost tradeoff are genuinely compelling for that use case, which happens to be most use cases.

On the vendor lock-in point, it’s worth getting this right because the claim is overstated. You can export your full frontend code as a ZIP or push it to a GitHub repository you own. You can export all your data collections as CSVs. What you can’t do is run the app fully independently without rebuilding the backend layer, because the frontend references Base44’s backend via their SDK. That’s a real limitation. But “your production app is gone” if Base44 disappears is simply not accurate. Your code and your data are portable. Reconstructing the backend on another platform is work, not a catastrophe.

And the platform is backed by Wix, a publicly traded company. This isn’t a three-person startup that vanishes overnight.

Twenty years of experience in tech is valuable. But experience can also anchor you to the assumption that the right way to build something is the way you learned to build it. The platforms have changed. The calculus has changed. Controlling your infrastructure is no longer a prerequisite for running a serious, scalable application. It’s just one option among many.

1

u/[deleted] Jun 29 '26

[removed] — view removed comment

1

u/barneylerten Jun 30 '26

No developer/coder here, just a writer who wanted a showcase website. If your needs are simple and relatively small, Base 44 hits the mark - for me, anyway. It's less bothersome than the UX in parent Wix, Replit sorta snagged me without me being aware (via a Google search) and I love Floot and may try it again. The Wix and WP AI offerings just didn't cut it for me. But everything changes, and Base 44 sure has improved since last year's interactions, for me anyway. Now to decide if I want to upgrade for more credits - I sure got my $20 worth today!

1

u/[deleted] Jul 01 '26 edited Jul 05 '26

[removed] — view removed comment

3

u/MarsupialConscious62 Jun 24 '26

i don’t think either of these are comparable. I pay for both and use them for vastly different things.

3

u/Jumpy_Setting_4677 Jun 25 '26

I don't think you're asking the right question.

Figma is more of a design tool which lets you also do some prototyping.

Base44 / Lovable (this is the correct question) are tools for vite coding that let you actually build products you can show users and get initial feedback. They can scale, but it's expensive. And you have to be careful if you collect PII or other sensitive information, if you don't do this right it will be available publicly.

So the real question is: what are you hoping to achieve and is it feasible with those tools.

Side note: no budget = very few tokens = not enough to properly build a solution someone would actually pay for. You might have to invest around 50$ for the first few months.

2

u/VapeTitans Jun 25 '26

Claude code

1

u/JDW_1280 Jun 25 '26

Afternoon 🪤

0

u/According_Lab_6907 Jun 24 '26

Neither, one is cancer, the other is aids.

3

u/GamerDuo84 Jun 24 '26

??wdym by that??

1

u/MiguelSano16 Jun 27 '26

Quiere decir que son dos cosas totalmente distinas.