GDG Coding Jams
Build with AI. Together.
Share
← Back to the jams
Tool guide

🎨 AI Studio

Open a tab, describe what you want, watch it appear. Nothing to install before the doors open.

👤

For builders who don't write code day to day — designers, PMs, students, anyone with an idea and a browser.

Before you arrive

A pre-flight checklist.

Do this at home, on decent wifi. Half the workshop time is otherwise lost to setup — this gives it back. Turning up without it is still fine; pair with a TA.

The Google Cloud credits aren't for this path — and you don't need them.

The credits your organizer hands out attach to a Google Cloud billing account, which is the Antigravity path. AI Studio doesn’t touch any of that: sign in with your Google account and start building. Nothing to claim, nothing to bill, nothing to configure.

It’s free but not unlimited — if you push it hard you may be asked to slow down for a moment. Wait it out rather than starting over; you won’t lose anything.

Need heavier or longer-running usage than that? Switch to the Antigravity path, where the credits do apply.

Install these

Nothing. That's the point.
  1. 1
    A browser

    Anything modern. AI Studio runs entirely in the tab — there's no IDE to download, no package manager, no terminal.

  2. 2
    A Google account

    Sign in at aistudio.google.com and you're in — no key, no project, no setup. Use the same account you'll share your build with afterwards.

    Open AI Studio

Worth having

Optional, but it makes the session smoother.
  1. 1
    Your inputs, ready to go

    If your track needs a photo, a dataset or a block of text, have it on the machine before you sit down rather than hunting for it mid-build.

The walkthrough

What you’ll do, step by step.

  1. 01
    Sign in

    Open AI Studio with your Google account. That's the whole setup — no workspace to create, no key to generate, nothing to claim.

    https://aistudio.google.com
  2. 02
    Hit + App in the sidebar

    That's it, that's the step. Everything you build lives in there — no project scaffolding, no install, no terminal. Describe what you want and start.

  3. 03
    Shape the result

    The first version is never the one you keep — that's the point of working this way. Narrow it down: change the tone, fix the layout, drop the feature that isn't earning its place. Small, specific asks beat one long one.

  4. 04
    Get a link you can share

    How to get from a working prototype to something you can send people — and onto the showcase.