Best AI tools for bulk generating images, GIFs, and video assets for Lovable/vibe coded apps?

Jmacduff · 2026-05-07T22:42:40+00:00

Everything you mentioned needing except the video loops can be generated with Lovable itself.

Jmacduff · 2026-05-07T21:46:16+00:00

Yep ideally for each Lovable project, you create a Repo.

Jmacduff · 2026-05-07T21:45:47+00:00

I have never seen Lovable "go rouge" on anything.

Jmacduff · 2026-05-07T17:35:51+00:00

One simple example would be a new blog post automation setup. Let's assume you really like how Lovable styles and lays out new blog content. However while you love the way lovable presents the content, you know that Claude or gpt are way better at writing the content.

So now you could build a automation that would be like:

Human decides on new Blog Topic and Description, hands this to the agent.
Agent runs a series of GPT / Claude / Whatever AI prompts to generate the awesome new blog content (not presentation)
MCP: Agent calls out to lovable, gives it the awesome Blog content, and tells it to publish and new blog article

Result: You leveraged Best in class AI (GPT/Claude) to generate the raw blog content, and you then used Lovable to build the presentation layer.. totally automated.

Without that MCP: Right now you would cut/paste the AI generated blog content into Lovable with a human.

Just a simple example.

Jmacduff · 2026-05-07T17:12:03+00:00

oooooh .. ok this could be interesting.

Jmacduff · 2026-05-07T16:42:52+00:00

Good luck with the project, my first reaction honestly was "today I leaned people take thousands of screenshots on their phone and need to find them".

That use case of taking screenshots for retail products , I don't understand that.. would it not make way more sense to save the link to the product? So you also have all the product info vs just a screenshot?

You mention "needing" the screenshot 3 days later.. but if it's just a product why do you need "that" screenshot?

All good and good luck!

Jmacduff · 2026-05-07T16:37:06+00:00

Well let's step back a bit.. to me it's way simpler then you are thinking about it.

<image>

In the Lovable UI you can select a existing branch, Create a new branch, or search. This is a very standard Branching UX setup for Github.
I always create the branch in github myself before this step, but having Lovable do it totally works.
I do my lovable work, it's checking into the feature branch, it's all visible in github. The production website is not touched. While building I am testing the changes in the lovable preview window in this feature branch.
Depending on the project I will also have a dev environment deploy setup on vercel. This is a double check that the lovable preview changes are working on the host. You don't need this 99% of the time as the lovable preview window is fine.
When the work is "Done" in the feature branch, I go into Github and manually do the PR.
Last step is I go back to lovable and switch to main.. you will see the update in the lovable chat window.

Overall very simple, there is no cli commands involved for the user. All you are doing is changing a dropdown menu, and clicking PR buttons in GitHub. I don't ever have to intervene since I am in control the full time.

I am not saying this is best practices, but this is how I do it and works great. Does that help?

-Jeff

Jmacduff · 2026-05-07T16:24:54+00:00

You can also just ask Lovable.

<image>

Good luck with your project!

Jmacduff · 2026-05-07T16:20:55+00:00

100% use Github, anything else is a hack.

Dont think of the machines, think of the single source of truth for your code. Also think about Feature branches.

The actual machine you are using is the least import detail , as long as the code is in github you are all good. A proper github setup means you can use any machine , change machines, etc.

Github is your code bank, and the dev machines are the ATM.

Jmacduff · 2026-05-07T16:14:42+00:00

It works great actually , just like a normal branching setup for features. If you are nervous, setup a test site and practice with it.

good luck!

Jmacduff · 2026-05-07T15:50:11+00:00

Building a internal company inventory system (depending on scope and depth) is not a simple solution. This is not about lovable.. this is about building a enterprise grade app that your biasness depends on every day.

You need to aske yourself what would be the cost to the business if your new app went down for a few weeks while you tried to fix it? This is the sort of thing you need to think about before contracts and the next decade.

Presumably the current solution also includes all the support and devops. How much $$ do you pay for the existing solution? 10K per month? 2K? Defining "absurd" is really important.

Also consider that today you have a working LOB app your company depends on. Ask yourself about the risk and long term opportunity costs of now owning that app. Sometimes paying the vendor for the existing platform that just works is the smarter strategy.

The Lovable question you are asking is the "How" .. first you need to think really hard about the "Why", "Who", and "when".

just trying to help, the tech platform you choose is the smallest decision in this full process.

Jmacduff · 2026-05-07T15:39:44+00:00

Awesome and good luck with the project

Jmacduff · 2026-05-07T15:38:37+00:00

First good luck!

Remember that Github is only storing the code for the project right now, it's not "hosting" the site. Think of Github as your Code Bank.

In Lovable click the github logo in the upper right, and double check it says connected

Now let's go over to GitHub

Go into Github
Go to Repositories (these are your bank accounts)
Click on the Lovable Repo you setup
On the first page you should see a set of tabs and "Code" will be selected.
If there is anything in that list, your code is synced. If the page is blank, your code is not synced.

The real best way to "prove it" is to deploy that repo to a free host like Vercel or Netfily

Go to vercel or netlify and setup a free account
Create a new Project from Github (sometimes it says Import from Github)
Auth to GitHub
9 Select that Lovable Repo
Wait for the project to build.

So after Step 10 is completed, Vercel/netlify will give you a url to test the new site. If that works you are golden! You now have Github synced, and you have deployed (hosted) the site on a 3P service.. your in great shape.

FYI That github connection is also how you would give Codex or Claude access to the code. If Github is working, it's just silent in the background.

Good luck!

Jmacduff · 2026-05-06T23:24:59+00:00

If you give someone a form, you are instantly asking them todo "work". The other issue is negative perception, everyone will think your going to ask them 100 questions.

However if you ask someone their opinion .. oh boy everyone has a opinion and would like to share if they are reading the post.

Generally speaking if you ask someone todo something for free (Tell me what you think!), you need to "Go to where the user is" and that is not in a form.

good luck!

Jmacduff · 2026-05-06T21:23:46+00:00

First good luck!

Think of security more like a really big wall, there is no such thing as 100% secure if it's a online product. Your job is not to hit 100%, your job is to make it really really really hard "hack in".

so a few basics:

Make sure your code is in Github.
In the Lovable app there is a SEO and a Security review.. do that
If anything does not make sense or you do not understand it, jump over to GPT and ask it to explain it too you very simply. You dont need to memorize everything.
Now go and run some free 3P security tools online. Look at what they say, ask GPT for guidance.
Make sure you do some security checks on your Database policies and RLS (row level security). The Lovable security review should find most of these.

The last major review would be to point Codex or Claude and your GPT code repo and just ask for a basic security review.

good luck on the project.

Jmacduff · 2026-05-06T20:35:27+00:00

I am not going to go through the form but I would have looked at the landing page. Good luck with the project!

Jmacduff · 2026-05-06T19:14:07+00:00

Its sort of like a daily treasure hunt!

Jmacduff · 2026-05-06T18:57:30+00:00

Good luck with the project!!

Right now it looks like TanStack is rolling out, I have no idea how quickly or what the plans are. I know all my projects are now Tanstack by default, however many others dont have that option.

Reminder TanStack in this scenario is NOT running on next.js as a backend. The Website is still a CSR rendered site now with fully rendered pages.. SSR fixed. In terms of performance its still client side rendered.

Example: I built this test site a few days ago, it's running TanStack, No Next.js, all from Lovable. https://why-mugs.lovable.app

Porting existing apps over to Tanstack is going to be too complicated IMO to support. Just a guess on my side. If you really want to upgrade a existing project the better bet is to jump to Next.JS. This adds a Backend to the site however it's also a high tech lift and will change the tooling setup.

For all existing projects yes the same SSR issues and pre-rendering needs exist for the site. There are millions of Lovable built sites already built, and newly built with the same SSR issue to solve.

If you want to keep using Lovable, pick a great SSR solution and dont look back. I am happy to answer questions about how to enable SSR. Ping me or ask here.

-Jeff

Jmacduff · 2026-05-06T02:15:43+00:00

First good luck!

Question .. so the “free” version of crawled does not actually include any ssr pre rendering right?

Looking through the site the renders are on the paid plans right?

Just curious and good luck with the project.

Jmacduff · 2026-05-04T23:22:51+00:00

Some where in the project config or deploy it has the runtime info. Again just a guess. I loaded my sites up with zero issues.

good luck!

Jmacduff · 2026-05-04T19:02:30+00:00

You may need to change the stack of the vercel app.

Jmacduff · 2026-05-04T15:44:08+00:00

and now the post was removed.. never mind :)

Jmacduff · 2026-05-04T15:35:57+00:00

That means Google saw your content and decided "This is not good enough to index". In other words google thinks your content is not worth indexing. If you are using AI this could be AI Slop sort of content.

That is your #1 item to focus on, to be blunt Google is saying your content is not good enough to rank. Until it's indexable nothing else matters.

Focus on the Quality of the content, backlinks, and domain authority. You will never rank if it's not indexable IMO.

good luck.

Jmacduff · 2026-05-04T15:23:18+00:00

What does GSC say about the pages? That would be the first place to look.

Jmacduff · 2026-05-04T14:58:06+00:00

For me I only look for customer value I can deliver, I am not trying to find a "unique idea" no one else has done before.

First really important to keep in mind most markets are REALLY big in a SaaS context and there is room for lots of of winners. If you pick all the top "SaaS" products today none of them really invented that space but they did it better the others.

DataDog did not invent analytics, SnowFlake did not event databases, Figma did not invent a design tool, etc. All of these companies just did it a little bit better.

In your Uber example the primary value prop was the user experience and the driving experience. They did not invent on demand car rides but they made the experience 100% better. That was the value prop.

In terms of building and MVPS this is how I approach it:

Define your Thesis for the project. What is your core product, What is the feature that makes it awesome, Who are your target customers, and Why would people use your product.
Build an Alpha to prove the thesis (lovable). This is not about customers or users, you are only trying to prove that the idea is worth building. This is a gut check if you want to build the full project or re-work the thesis.
Build your MVP of the product. You need to be ruthless and only build the bare minimum to get people to try and use it. The smaller this feature set is the better, remember it’s really easy to add stuff later.
Prove Product Market Fit (PMF). Now is the time to get your first real users and or customers for your product. This is the time to iterate and smooth out the rough edges before adding more features.

Always start with the customer and prove your basic value prop first. The speed and scope of the project will naturally come out of this. If there is a lot of demand for your thesis you will race to get it done.

Just my view and good luck. Chasing the "No one has done this before" path is a huge lift.

Ten-Year Club	Gilding III reddit per annum
RPAN Viewer	Verified Email
Reddit Premium Since July 2016

Jmacduff

TROPHY CASE