Rendimiento y costes

Your app works — but is it fast, and what does it cost to run? Vibe-coded apps often have hidden performance problems and surprise AI/API bills. This lesson shows you how to keep both under control.

You don't need deep optimization skills. You need a few habits and the right questions to ask your AI.

The biggest mistake is guessing where the slowness is. Measure first. A quick timer around suspicious code tells you the truth — often the bottleneck isn't where you'd expect.

This snippet times how long a piece of work takes.

A classic performance killer is calling a database or API inside a loop — one call per item, hundreds of times. The fix is usually to fetch everything in one go.

Spot the difference.

You can hand your code to AI and ask it to hunt for the slow parts. Be specific about what you suspect so the answer is focused.

If you compute or fetch the same thing over and over, save the result and reuse it. This is caching. A simple in-memory cache can turn a slow repeated call into an instant lookup.

On the web, performance is often about how much you send to the browser. Huge images and bloated JavaScript bundles make pages load slowly, especially on phones.

Ask your AI tool to slim things down — it knows the modern tricks.

If your app calls an AI model (like the Claude or OpenAI API), every request costs money based on tokens — roughly, the amount of text in and out. A popular app making many calls can run up a real bill fast.

The instinct to send huge prompts "just in case" is what blows budgets. Send only what's needed.

Several levers reduce AI spend dramatically:

• Use a smaller/cheaper model for simple tasks; save the powerful one for hard ones.
• Shorten prompts — trim filler and only include relevant context.
• Cache answers for repeated questions instead of re-asking the model.
• Limit the output length when you don't need a long reply.

The simplest way to avoid a shocking bill is to set a spending limit and an alert. Most API dashboards (Anthropic, OpenAI, your hosting provider) let you cap usage or get notified at a threshold.

Turn this on before you launch, not after the bill arrives.

Balance matters. Spending days shaving milliseconds off an app with ten users is wasted effort. The rule: make it work, make it correct, then make it fast — and only where it actually matters.

Measure, fix the biggest real problem, and move on. Premature optimization makes code complex for no benefit.

Before you ship, run through this with your AI:

• Measured the slow parts — not guessed.
• No database/API calls stuck inside loops.
• Repeated expensive work is cached.
• Frontend ships compressed images and split JS.
• AI calls use the right-sized model and trimmed prompts.
• Spending limits and alerts are set.

You learned to keep vibe-coded apps fast and cheap: measure before optimizing, avoid calls inside loops, cache repeated work, slim down the frontend, and control AI/API costs with smaller models, trimmed prompts, caching, and spending alerts.

And don't over-optimize — fix what matters, where it matters. That wraps up Productionizing AI Code: your apps are now tested, secure, maintainable, fast, and affordable. Real builder territory!