Build · founder · 6 min read

Google I/O 2026 'Code the Countdown': How to Get Your Vibe-Coded Project on the Keynote

Google opened a vibe-coding contest where the best non-technical submissions get featured at the I/O 2026 keynote. The deadline is May 6. Here's how to play.

Published May 2, 2026 ·

google google-ai-studio gemini vibe-coding news founders events

On May 1, Google opened public submissions for Code the Countdown — a vibe-coding contest where the prize is having your project run on the live countdown clock at the I/O 2026 keynote on May 19. The deadline to submit is May 6. The whole exercise takes a non-technical builder roughly 30-90 minutes if you’ve ever opened a Gemini app or Google AI Studio in your life.

For PMs and founders who’ve been meaning to “actually try this vibe coding thing,” this is the lowest-stakes possible on-ramp. You don’t need to ship anything. You don’t need to handle data. You don’t need to deploy a backend. You just need to make a single creative thing that visibly features one or more numbers between 1 and 10. Below is how to think about it, what to make, and what to do if you want your submission picked.

What Code the Countdown actually is

Google’s I/O keynote always opens with a countdown timer. For 2026, that countdown is replaced by five browser-based games and animations, all built using Gemini and all open-sourced in Google AI Studio so anyone can fork them. The submission window for additional pieces is open to the public. Google says they’ll pick the best ones and add them to the keynote rotation, with a credit to whichever social handle you submit alongside your idea.

The brief is one line: build something creative that features at least one large number between 1 and 10 — or all of them. Examples Google itself ships in the demo set include a synthesizer with ten keys, an animation where digits transform into animals, and a simple incremental clicker where the goal is to reach 10. The point is the numbers have to be visible and meaningful in the experience, not just hidden in the code.

Why this is the right first vibe-coding project

Three things make Code the Countdown an unusually friendly place to start.

First, the constraint is small enough to finish in one sitting. Most “make your first AI app” projects fail because the brief is open-ended (“build something that solves a problem you have”), and you spend three hours scoping before you build anything. Here, the constraint is concrete — one creative thing, numbers 1-10, browser-based — which means you can get to “working prototype” in under an hour.

Second, it doesn’t store user data, take payments, or touch anything regulated. The whole reason vibe coding has a security reputation problem is that people use it to ship apps that handle personal information without ever auditing the code. Code the Countdown is the opposite end of that spectrum. The blast radius if your submission is buggy is “the animation looks weird.” That’s the right risk profile to learn the medium on.

Third, the tools Google wants you to use are free. The official submission flow points at the Gemini app’s Canvas feature (free tier works fine for a small project) or Google AI Studio’s Build tab, which we covered last week when Google rebuilt it into a real vibe-coding environment. No subscription needed. No credit card.

What to actually build

If you stare at the brief for ten minutes and nothing comes to mind, here’s a list of patterns that fit the constraint and are tractable in an hour or two of prompting.

A digit-themed mini-game. Pick one number 1 through 10. Build a tiny game where that number is the goal, the score, or the hazard. “Match three to a target of 7,” “click the bouncing 4 before it disappears,” “stack blocks until you build the number 10.” Keep the visual style flat and bold — Google’s reference set leans graphic, not photo-realistic.

An animated visualization of the numbers transforming. A canvas where 1 morphs into 2 morphs into 3, with each transition being a different visual metaphor (1 splits into 2 like a cell, 2 stretches into a 3, etc.). This is a great first-prompt for Gemini because it reads as a clear sequence of states. Ask for it in SVG and it’ll be sharp at any keynote-screen resolution.

A tiny synthesizer or generative-music piece. Ten keys, ten notes, ten patterns. Browser audio is one of the things Gemini Canvas handles surprisingly well — the Tone.js and Web Audio APIs are well-represented in its training set. If you’re more comfortable with sound than visuals, this is a strong fit.

A clicker or incremental game where 10 is the win condition. The reference set already has one of these, but the design space is huge — make yours visually distinct and tied to a metaphor (10 customers, 10 launches, 10 employees) rather than abstract points.

The thing to avoid: anything multi-screen, anything that needs a database, anything that depends on real-time multiplayer. The submissions Google will favor are ones that look great in 8 seconds on a 4K screen at the keynote, not ones with depth or persistence.

How to actually ship it

Open Gemini at gemini.google.com and switch to Canvas mode (the button below the prompt). Or open AI Studio at aistudio.google.com and pick the Build tab.

Start with one prompt that describes the whole thing. “Make a single-page browser app where the digits 1 through 10 each represent a different musical note, arranged as colorful circles in a row. Clicking a circle plays the note and animates the digit. The whole thing should use only HTML, CSS, and JavaScript — no frameworks, no external libraries except Tone.js from a CDN. Make the visual style bold and graphic, suitable for displaying on a large screen.”

Iterate by describing what you want changed in the same chat — “make the colors warmer,” “add a tiny visual ripple when a note plays,” “scale the digits up so they fill the canvas.” Don’t try to describe the whole app perfectly upfront. The vibe-coding loop works because each turn is cheap.

When it looks good, copy the code or use the share button to publish a public AI Studio link. Then go to the submission form and paste in your link, your idea description, and at least one social handle so Google can credit you if you’re picked.

What to do if you don’t get picked

The usual outcome of contests like this is that 95% of submissions don’t make the keynote, and most participants treat that as a failure. It isn’t — the actual prize is that you now have a small, working, vibe-coded project you built in an evening, which is a far more useful PM credential than reading another comparison post about Lovable vs. Bolt. Stick the AI Studio link in your portfolio. Drop it in your “things I built” doc. You can repurpose it for a portfolio piece, an internal demo, or as the seed of a real product.

The deadline is May 6. The keynote is May 19. If you’ve never tried vibe coding, this is a notably gentle place to start, and you don’t have to wait for permission to begin.

Related reading

• Google AI Studio Just Became a Real Vibe Coding Tool
• Vibe Coding for Non-Technical Founders
• Best AI Tools for Non-Technical Founders