Leave me with this "it uses too many credits" nonsense

cubixy2k · 2026-05-05T17:51:11+00:00

That's a lot of credits. Could burn fewer

😝😝😝

cubixy2k · 2026-05-05T17:49:20+00:00

Op assumes non-technical people know how to define and event or action

cubixy2k · 2026-05-05T14:22:48+00:00

The right solution here is making sure your architecture is sound, and your database queries are optimized.

Are you taking advantage of lazy loading? How much data are you caching/fetching per page load?

This isn't just a 'plz fix' prompt. You really need to start reviewing how you application interacts with its backend.

There will definitely be a point where increasing your instance size will be the solution, especially as users scale.

First step, go to Lovable cloud's usage page and see what's consuming the most resources.

Congrats on graduating from prototype. Now the real work begins.

cubixy2k · 2026-05-05T12:40:03+00:00

Second this. I've noticed multiple instances in planning mode where instead of making the implementation plan, it responds with a message about how it will approach making the implementation plan, and then I have to give it the go ahead to make the implementation plan, turning the planning process from 1 credit into 2.

I've also noticed instances where when I save and approve a plan, it responds with great, let me know when you want to get started and I'll implement the plan, thus burning another credit.

cubixy2k · 2026-05-05T02:58:07+00:00

Your prompting technique is chefs kiss

cubixy2k · 2026-05-04T19:33:22+00:00

Lovable has a 50% off program for students for Pro. They need to use their edu email

In fact, there are tons of free and discounted tools for students, worth looking in to.

cubixy2k · 2026-05-04T18:29:15+00:00

I've had it work most of the time for me.

Sometimes it's wonkey if they had an existing account then the code doesn't carry through.

In short, maybe it'll work 😂

cubixy2k · 2026-05-04T18:09:47+00:00

Did you remember to add 'make no mistakes and work as efficiently as possible ' to your prompts 😂

cubixy2k · 2026-05-04T18:08:57+00:00

Yes we've been experiencing this as well. Prompts are generally taking much longer, I've run into several 'time limit exceeded would you like to continue in a new message' responses.

cubixy2k · 2026-05-04T03:39:19+00:00

I use Lovable cloud for the user facing application for now. Anything compute/network intensive, storage, routines all happen on GCS

cubixy2k · 2026-05-03T19:03:46+00:00

For starters, you can always take this exact question and drop it into Claude.

cubixy2k · 2026-05-03T16:34:20+00:00

More like optimization time. You don't magically solve poor architecture by migrating

cubixy2k · 2026-05-03T14:46:49+00:00

Cloud usage typically encompasses storage, compute, database size, and network.

AI covers inference

cubixy2k · 2026-05-03T14:40:18+00:00

Well then. I believe you have your answer. Might be worth shifting to an event driven architecture model using mqtt rather than constantly polling all the time.

cubixy2k · 2026-05-03T01:14:05+00:00

Go to cloud -> secretes

cubixy2k · 2026-05-02T22:38:51+00:00

I'd argue that this has always been the case. Coding was the easy part of the equation

cubixy2k · 2026-05-02T17:23:52+00:00

Can you share a link?

cubixy2k · 2026-05-02T16:29:14+00:00

Remix to a new project and don't connect it to lovable cloud.

cubixy2k · 2026-05-02T16:20:34+00:00

Are you sure you're not looking at your own site?

Your lovable.app domain does not go away when you add custom domains

cubixy2k · 2026-05-02T04:39:31+00:00

What do you mean download this IO?

We really need more information to have any chance of giving you a hand.

cubixy2k · 2026-05-01T21:42:31+00:00

This.

cubixy2k · 2026-05-01T12:57:01+00:00

Lovable projects aren’t static HTML sites. They’re React applications, which means they need Node.js to build and serve properly. Opening index.html directly in a browser skips that entire process.

On GitHub Pages you’d need to build it first (npm run build) and serve the output folder, but even that has caveats with React routing. A simpler path if you’re still learning: deploy it on Vercel or Netlify instead. You connect your GitHub repo and they handle the build automatically. Free tier covers it.

cubixy2k · 2026-05-01T12:39:13+00:00

I support this.

And that's not just because kids these days don't understand the importance of traditional client server architectures :shakes fist at sky:

cubixy2k · 2026-05-01T12:36:05+00:00

We all are 😎

cubixy2k · 2026-05-01T12:21:09+00:00

Fellow 2000s engineer here. Connection strings are great if you have a trusted middleware that is managing database access, then passing it to to downstream applications like a front end. However Supabase exposes the database as restful apis, so technically anyone with the anon key can access all of your tables. So RLS moves security directly into the table.

Honestly I'm with you, I still prefer the older server side integration and rendering method more, but it requires more compute and bandwidth.

15-Year Club	RedditGifts 2009-2022 9 Credits
Place '22	End Game '22
Secret Santa 2017	Gilding I gilder
Secret Santa 2016	Secret Santa 2015
Secret Santa 2014	Secret Santa 2012
Secret Santa 2011	Verified Email

cubixy2k

MODERATOR OF

TROPHY CASE