0
← Journal index

AI / Wanderings 2025

Vibecoding: How to Build Products 10x Faster (And Actually Enjoy It)

Google's Antigravity shifts you from writing code to orchestrating agents. Here's how to actually use it.

By Martin Uetz5 min read

The way we build software just changed.

I don't mean incrementally. I mean fundamentally. From "write code" to "orchestrate agents."

Google Antigravity is the tool, but the shift is bigger than that. It's a change in how you approach the problem. And once you feel it, you can't go back.

From Code-Writing to Orchestration

Traditional dev workflow: you sketch the feature, write the code, debug the code, refactor the code, test the code, ship the code.

Vibecoding workflow: you describe what you want, the agents write the code, you review the code, you test the behavior, you ship.

The difference is that you're no longer implementing the solution. You're describing the solution and letting agents implement it.

This seems minor. It's actually transformative.

Why? Because 70% of traditional coding isn't "clever thinking." It's boilerplate, patterns, searching through Stack Overflow. That's exactly what agents excel at. And when agents handle that, you're left with the 30% that actually requires human judgment: "is this the right approach?" "does this match the intended behavior?" "does this feel right?"

The Stack That Actually Works

You don't need to use Google Antigravity. But if you're building web products, here's the practical foundation:

Frontend: Next.js + Tailwind

  • Next.js gives you routing, server components, deployment to Vercel in one click
  • Tailwind gives you styling without thinking about CSS architecture
  • Together they're the fastest path from "idea" to "something people can use"

Database: Supabase or Cloud SQL

  • Supabase if you want managed PostgreSQL with auth baked in
  • Cloud SQL if you're already in Google Cloud
  • Either one: you get a real database without managing infrastructure

Payments: Stripe Checkout

  • Antigravity has built-in workflows for Stripe
  • You literally drag and drop "collect payment," it generates the integration
  • This saves weeks of integration work

Deployment: Google Cloud Run

  • One-click deploy from your local environment
  • Scales to zero cost when you're not using it
  • Antigravity has native Cloud Run workflows

Mobile: Capacitor

  • Convert your web app to iOS/Android without rewriting
  • Takes a Next.js app and generates native wrappers
  • You're not maintaining two codebases

The Antigravity Workflow

Start in Planning Mode. Master prompt approach.

You describe what you want. Detailed but conversational. "I want an e-commerce app where users can browse products, add to cart, check out with Stripe, and see their order history."

Antigravity breaks this into:

  • Data models (Product, Order, OrderItem, User)
  • API endpoints
  • Frontend components
  • Workflow integrations

You review each piece. You can say "change the Product model to include inventory_location" and it regenerates everything downstream.

Then you connect to the MCP Store—managed connection providers for AlloyDB, Cloud SQL, etc. One click. You're connected to a real database.

Drop in a Stripe Checkout workflow. Drop in a Cloud Run deploy workflow. You've got a complete pipeline.

Why This Is Actually Better

The objection is always: "won't AI code be bad?"

Sometimes. But here's the thing: the code Antigravity generates is better than average junior developer code. It's boring, clean, follows conventions, includes error handling. It's not creative. It's competent.

And you're reviewing it. If something's wrong, you see it immediately. You fix it or regenerate. The feedback loop is tight.

Compare that to traditional dev: you write code, you test it, you find bugs three weeks later in production. The feedback loop is slow.

The Real Advantage

The speed isn't just about writing code faster. It's about iteration speed.

You want to try a different UI layout? Five minutes. You want to change the database schema? Regenerate the models and migrations. You want to add a new workflow? Describe it, review it, ship it.

This lets you explore the product space instead of committing to an initial design and defending it. You can build three different approaches and see which one actually feels right. That's how you discover what users actually want instead of what you thought they wanted.

The Mindset Shift

This requires unlearning something: the idea that code quality is measured by cleverness.

Good code is boring. It works. It's maintainable. It handles edge cases. Most importantly, it solves the right problem.

Antigravity excels at boring code. It's terrible at novel algorithmic problems. But most products aren't novel algorithmic problems. They're "how do we move data through systems in sensible ways." That's exactly what agents do well.

Getting Started

If you're building something today:

  1. Describe it to Antigravity in detail (one paragraph per feature)
  2. Review the generated schema and endpoints
  3. Build the frontend component by component
  4. Connect to Cloud SQL or Supabase
  5. Add payment flows
  6. Deploy to Cloud Run
  7. Wrap with Capacitor if you need mobile

Total time: 2-3 weeks for an MVP that would take months with traditional dev. And it's actually a better product because you iterated faster and found the right approach.

The Awkward Truth

This means traditional software engineering—the years of learning frameworks, optimization, debugging—has less moat.

But it also means you can build what used to require a team of five developers. You and an AI, moving fast, iterating, discovering.

That's worth something. Especially if what you want is to build products people actually love instead of becoming a .js framework expert.

Vibecoding isn't the future of software development. It's the present, if you're willing to shift how you think about it.