GDG Coding Jams
Build with AI. Together.
Share
← All tracks
Track

Put it on the map

Build an application that uses real map data. You decide what it shows.

2-hour jamYou choose what to buildWorks in both tools
The requirement

Your application must display a real location on a map and respond to what is there.

That is the only rule. What you build inside it is yours to imagine — there is no spec to follow and no right answer. Bring the idea you have been sitting on, or invent one in the room. The best builds are the ones nobody saw coming.

If you want a starting point

Some directions people take

Optional. These are examples, not a menu — the point of this track is that you choose.

  • A quiz about the area around a chosen location
  • A walking route with a generated description for each stop
  • A comparison of two neighborhoods
  • A recommendation based on where the user is
While you build

Things to keep in mind

  • Include real location data in your prompts. Prompts without location context return generic results.
  • Build against one city you know well. You will recognize an incorrect result immediately.
  • Handle the case where a location cannot be found.
Share your build →

Built something? Two minutes, and it lands in the showcase. Half-finished is fine.

The 2-hour jam rhythm

How the session flows

Every Coding Jam follows the same shape, whichever track the room takes.

  1. 0:00 – 0:15
    Intro

    Grab a name tag and a slice, say hello to the instructor, and meet the people either side of you — you'll be asking them things later, so it pays to know their names now. Low pressure, high creativity, ship something messy. Then a quick word on what the room is building tonight, and you're off.

  2. 0:15 – 0:30
    Credits & setup

    The instructor shares the Google Cloud credits with the room. Everyone gets their environment ready — whichever tool they brought. Nobody should be installing anything once the build starts.

  3. 0:30 – 1:35
    Build

    Heads down, and enjoy it — this is the part everyone came for. The agent does the typing; you decide what it's making. Ask the room when you get stuck; someone two seats away hit the same wall ten minutes ago. Want more structure? The codelab walks the spec-driven route — Setup → Plan → Review → Build → API → Verify — but nobody has to follow it.

  4. 1:35 – 2:00
    Share & submit

    Show the room what you made — two minutes, screen-shared from your seat. Half-finished is welcome; the wobbly ones are usually the most interesting. Say what surprised you along the way, and cheer for everyone else while you're at it. Then submit your build before you leave. This is the one thing not to skip — it's what puts your name and your chapter on the showcase, and it takes about two minutes.

Pick another track

All independent. Start anywhere.

See all tracks →