Google · from experience
THE SOURCE · THE CASE STUDY ON KAGAMI.BGAI Studio: an interface from one big brief
Get a React interface from one brief, without invented facts and without spending the daily limit on small fixes.
Google AI Studio in real work: a website in one night
The numbers, the lessons and where each number comes from are in KAGAMI's article. Here is only the recipe. →
The prompt
Build a web app "<Name>": <one sentence on what it does>. The interface is entirely in Bulgarian (lang="bg"). It works on phone, tablet and desktop (responsive; PWA if it must be installable). ## Who it is for <users, age, what they do every day>. Smallest text 15 px, body text about 19 px. ## Screens 1. <Screen> — <what is on it and what happens on tap>. 2. ... ## Data and server We write the server. The interface calls only these endpoints: <GET /api/... → fields>, <POST /api/... → fields>. Without a server the app starts in demo mode, clearly marked "Demo data". On error it shows a clear message in Bulgarian and never switches silently to demo data. ## Rules - Do not invent facts: phone numbers, addresses, prices, statistics, licences, clients, incidents. Where there is no data, write "to be confirmed". - The text speaks only for <the company>. No vendor names, internal tools or notes to the developer. - Do not add login, registration, payments or AI features unless requested here. - Accessibility: aria-label on all icon buttons, contrast, keyboard. Do everything at once in this round.
The tool: the steps
The proof
GOOGLE · AI-STUDIOREV 0.1
- model
- Gemini 4 Argon (built into Build)
- interface with 7 screens
- 11 min 6 s · 29 files · 5,188 lines
- second round
- 2 min 41 s · 10 files
- a client website
- one night (≈ 7 h 20 min), live on vtasz.com
- date
- 29–31.10.2026
checkedrun by us; the numbers come from our records