The short answer
Pick Google AI Studio when you want a quick demo or a throwaway web app, built in the browser with Gemini already inside it. Pick Claude Code when you are building software you will maintain, deploy and hand to real users.
That is not a guess; it is how both of us described our own habits in Episode 38 (April 2026). We both love AI Studio. We just do not ship production tools from it.
What we built with each
Google AI Studio
- Weather and time app for Los Angeles and Nashville: built live on launch day, "definitely the fastest fastest thing we've built so far" (Episode 18, at 29:01).
- Mirror, Mirror on the Wall, the Guess My Costume app and the Trick-or-Treat route planner: our Halloween week, when both of us built in AI Studio "pretty much exclusively" (Episode 19).
- Bito Slack bot prototype: a mock Slack bot for our guest's product, from a basic prompt (Episode 23).
- AI start-of-care packet generator: Sam pasted a ChatGPT PRD into AI Studio with Gemini Pro and had it in "four or five different tweaks, probably in the span of thirty minutes" (Episode 24).
Claude Code
- ScreenEval: full-stack recruiter coaching app, about six hours between meetings, about to go live to recruiters (Episode 29).
- Offsiteio estimator and client presentation generator: started in Claude Code, moved to Codex for bug fixes, on Supabase and Amplify. "We're using it every day," and the first client it was shown to booked their biggest offsite yet (Episode 38, at 07:59).
- Internal web app redesign: Claude Code took a Claude Design handoff and had the whole app redesigned and live in about thirty minutes (Episode 40).
- Sam's ATS, the Kalshi trading bot and the candidate highlight reel builder.
The pattern is plain: every AI Studio build is a demo, a prototype or a one-off for an episode. Every Claude Code build is something a team uses.
Head-to-head
Sam asked Jordan directly how he picks a tool. Sam's own answer first: throwaway, quick demo, "I'm typically doing it in Google AI Studio. Otherwise, I'll probably start it in Cloud Code and then eventually transition to Codex." Jordan agreed:
I think it's kind of the same. You know, I think, like, each of these tools kind of, in my opinion, lives in, like, a different vertical. So, you know, if I'm building something that's like a big piece of software, then it's gonna fall into the vertical of, like, you know, cursor, clawed code, or or OpenAI or codex.
— Jordan Metzner, Episode 38
AI Studio also does things Claude Code does not try to do. In the same episode Jordan showed its model picker, Gemini Pro research with Google Search grounding, image and music generation, and a screen-share mode where Gemini helps you while you work on a website (at 13:50). It is a toolbox as much as an app builder. He added that sometimes he just asks Claude in the browser to build something, because "it does a great job there as well."
At 16:16 he put Google AI Studio, Lovable and Bolt in the "first column" for building a quick demo.
Where each one fell short
Google AI Studio. It is not where we put lasting software, and Jordan admits the API-key setup is "a little complicated." When Jordan launched it in Episode 18, he compared it to "Lovable and Bolt and vo.dev and even like Codex and and Cloud Code," with the difference that "you can do it all in the browser." That convenience is also the ceiling for us.
Claude Code. Slower to a first result and less friendly. Sam's ScreenEval took six hours, not thirty minutes, and still needed recruiter feedback and bug fixes after launch. Jordan's main complaint from Episode 35 was that it would make mistakes "but be confident that there were no mistakes," which is why Sam's Offsiteio estimator moved to Codex for fixes.
Which one we reach for now
Both, in sequence. Jordan still loves AI Studio "for just building out little web apps because it's it's so fast and so clean and gives you good inspiration" (Episode 38, at 16:16). Anything that needs to last starts in Claude Code, and often ends in OpenAI Codex.
If you are new, start in AI Studio to see your idea on screen in minutes. When people start asking to use it every day, rebuild it properly in Claude Code. For the next comparisons, see Claude Code vs OpenAI Codex and Google AI Studio vs Lovable.
FAQ
Is Google AI Studio as good as Claude Code?
They do different jobs for us. Jordan puts Google AI Studio in the column for building a quick demo, and Claude Code with Codex and Cursor in the column for a big piece of software.
Can Google AI Studio build a real app?
It builds working web apps fast, and it can deploy, push to GitHub or download the code. Our production tools, like ScreenEval and the Offsiteio estimator, were built in Claude Code instead.
Which is easier for beginners, Google AI Studio or Claude Code?
Google AI Studio runs in the browser with Gemini built in and suggests features as it builds. Claude Code runs in the terminal; Sam called it a pretty intense tool the first time, though he built his ATS in record time with it.
How do you go from a Google AI Studio prototype to production?
We have not moved a single project from one to the other on the show. Our pattern is to prototype a concept in AI Studio, then start the real tool in Claude Code and often finish it in Codex.