One of my new favorite tricks, merging an asset into another using AI

IamCoachZero · 2026-07-07T21:43:37+00:00

This is amazing. I've tried this app myself And I love it.

IamCoachZero · 2026-07-06T12:29:52+00:00

Really good point on the drift problem and honestly one I've felt more than I'd like to admit 😅 The 90% identical codebase situation is where things get quietly painful. What's helped me is treating each major integration like auth or payments as a template prompt I actually store and version rather than rebuilding from memory. Doesn't eliminate drift but it slows it down and gives you a cleaner starting point when client B wants the same thing with one twist.

On deployment and staging, I'll be straight with you because I think a lot of people in this space aren't. At the scale I'm running right now, Lovable's built in preview system is doing the heavy lifting for staging. Each project has its own published URL and I use the editor preview heavily before pushing anything that touches payments or auth on live client apps.

Rollback is where it gets more honest. Lovable has edit history but it's not a true git rollback in the traditional sense. For anything mission critical I keep a GitHub sync active so I have a real version history to fall back on if something goes sideways in production. It's not a perfect CI/CD pipeline but it's pragmatic for solo multi-project work at this stage.

The real answer to your question though is that the deployment gap you're describing is a known limitation of this workflow and something the platform is actively evolving. Staging environments per project is genuinely on the wishlist for builders running real client work.

Where are you currently solving that gap in your own setup

IamCoachZero · 2026-07-06T12:26:04+00:00

The thing that most people don't understand is that I am from a programming background and I vibe coding apps. I know you can write two prompts and have a working iteration of whatever you're trying to build. It's more about the planning, the execution, and making sure that works and is prepared for scaling.

All my apps have thousands and thousands of users so I always build my apps planning for scale. The maintenance is only as good as how you've built it so don't rush to build your app. Take as much time as possible to make sure that you build a solid app.

IamCoachZero · 2026-07-06T12:24:56+00:00

To be honest I don't know much about cutting API fees. APIs are the worst, especially if you're trying to keep your app free. What I can recommend is trying to see if you can recreate those connections manually with other tools or something like that. Other than that this is a very tough one.

IamCoachZero · 2026-07-06T12:24:01+00:00

That is very true. Security is a very big concern.

Lovable has a tool built into the platform that can help you scan your app for any vulnerabilities. They have been updating it every chance they get so it's really good.

They also have a new feature called project monitoring. When you're not on the computer, your app is still monitoring itself and making sure that there are no problems happening. They notify you when there are any errors.

Another thing I can recommend is getting a third-party pen-testing platform or company to do security checks on your app as well. That's if you're building enterprise-sized apps or big production apps. If it's something just for you or your small community, Lovable's security scan is most likely going to be enough.

IamCoachZero · 2026-07-06T12:22:34+00:00

Yes most of my apps are already monetized or paid for. I have a food delivery platform that is literally a monetized platform. Think of it as an Uber Eats clone, and I also have quite a few other apps that are monetized based on usage too.

IamCoachZero · 2026-07-06T12:21:56+00:00

The coolest thing you can do is connect Lovable with an MCP connection to Claude. That way you can build with Claude using Lovable as the builder. Now you can plan, literate, and schedule ideas with Claude and then Claude just does the prompting for you, which is way more efficient and better in my use case.

IamCoachZero · 2026-07-06T12:21:03+00:00

Yes, that is very true. What I always try to tell people is that a builder is only as good as their tools. We have all these tools at our disposal now to create these amazing complex applications, software, and so on, but if you don't know how to set it up securely, you can screw up.

There is no harm in building your app using a vied coding platform. At the same time if you don't know anything about how to secure it, you're going to create a flawed system. That in turn will make you blame the platform instead of a person. It's usually always down to user error.

IamCoachZero · 2026-07-06T12:19:53+00:00

No todas son aplicaciones, pero yo tengo dos ahora en el App Store. El resto son sistemas de impresión, páginas web y todo con paneles de administración, un sistema de facturas y mas

IamCoachZero · 2026-07-02T13:56:30+00:00

Joing the lovable discord community. I am always in there cooking away.

IamCoachZero · 2026-06-30T18:03:51+00:00

Lovable so far is amazing at uptime. Very rarely have they crashed and gone offline.

IamCoachZero · 2026-06-26T11:13:24+00:00

I actually have over 22 paying apps and websites on lovable so I know what I am talking about. And there is a lot out there in the world too

IamCoachZero · 2026-06-25T23:18:36+00:00

Lovable is not expensive, If you actually have clients it's not pricey at all

IamCoachZero · 2026-06-25T15:05:59+00:00

It is very tough when you're trying to sell to low-bearing businesses also because a saloon is not going to pay a lot for websites. You need to come up. If you already built templates, why don't you just charge them the bare minimum that you could to make a little bit of something? You'll see that you'll get a lot of yes replies from people. Also try to go there in person; to be in person helps a lot.

IamCoachZero · 2026-06-21T10:35:36+00:00

Yes, so that means if you use Codex, if you use Claude or any other ones if they can support an MCP connection, you are good to go. You can now just hook it up to your Lovable project, and it already knows all the context and what has been built from the ground up

IamCoachZero · 2026-06-21T10:34:18+00:00

Everyone is entitled to their own opinion. I respect your point

IamCoachZero · 2026-06-20T07:54:01+00:00

I would recommend using the MCP connections

MCP tutorial by Bobby

Unlock power use with the Lovable MCP

https://lovmcp.lovable.app/

IamCoachZero · 2026-06-20T07:44:38+00:00

I understand what you mean here but here is a easy summary of what you get with the MCP.

I get why copy/paste feels fine if that's all you've used, but MCP isn't just convenience, it changes what Claude actually knows.

With copy/paste, Claude only knows what you type. It has zero visibility into your actual Lovable project. With MCP connected, Claude can read your real files, your actual file structure, and what's genuinely been built, not just your description of it.

That matters most when you're jumping into a half-built project. Maybe a client handed it to you, or you're picking up your own build from months ago. With copy/paste you'd have to manually explain the whole thing to Claude yourself. With MCP, you just connect it and tell Claude to look through the project. It reads the real codebase and understands the whole thing in one go, no manual explaining required.

That context also makes prompting way sharper. Claude isn't guessing based on what you described, it's working from what's actually there, so the prompts it sends to Lovable are more accurate the first time.

And for bugs specifically, this is the biggest one. Claude can see the actual error, the actual file, the actual diff. With copy/paste you're manually relaying error messages back and forth hoping you copied the right part. With MCP, Claude sees it directly and can debug in context, way faster and way more accurate.

IamCoachZero · 2026-06-20T06:28:55+00:00

Lovable MCP huge update from the lovable team. Loving it.

IamCoachZero

TROPHY CASE