[verdict][generated prompt][source: gemini.google.com]
Can I vibecode Google Gemini?
// the value is the network, the data or the infrastructure
A chat UI is easy, but Gemini's model access, Google ecosystem integration, multimodality, storage tie-ins, and platform distribution are not solo-buildable.
confidence: high
what it is: Google AI assistant bundled with Gemini Advanced and Google AI Pro
Buildability index · an editorial game
- Price 19.99 $/month weight: plus 2
- Time not realistically solo weight: minus 3
- Category ai assistants no weight
- Moat proprietary models · integrations · infrastructure scale weight: minus 5
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site gemini.google.com (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build a multi-model chat app with document upload and optional Google API integrations.
what you need
- LLM API
- hosted app
- optional Google OAuth/API access
- storage
- file parsing
Completes the model-platform set; useful comparison for structural no verdicts.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me a personal chat client on the Gemini API to replace my Google AI Pro
subscription with per-token billing. Requirements:
- A local web app: Node + Express + better-sqlite3, one page, binds to
localhost.
- Gemini API key in .env, with optional Claude and OpenAI keys too; a model
picker per conversation.
- Streaming responses with Markdown and code-block rendering; history in SQLite
with FTS5 search across old conversations.
- Upload PDFs and images and pass them through to models that accept them.
- System-prompt presets as .md files in ./prompts/, selectable per chat.
- Export any conversation to a Markdown file.
- No accounts, no telemetry; history stays on my machine, only prompts go to
the APIs.
- Out of scope: Gmail, Docs, and Drive integrations, and mobile apps. Do not
build Google Workspace OAuth; that ecosystem tie-in is the subscription.
- README: where to create each API key, a rough cost table per model, and state
that per-token billing can land above or below $20/month depending on use,
the model itself is only rentable. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- frontier models
- Google app integrations
- mobile/native distribution
- multimodal stack
- reliability
Why people still pay
They pay for model access and Google-native placement, not because chat UIs are hard.
moat: Proprietary models Integrations Infrastructure scale what a moat is
frontier model/platform ecosystem
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Msty (si apre in una nuova scheda) — The desktop core is $0, but the terms limit it to private non-commercial use; paid work needs a license.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Open WebUI (opens in a new tab) — Open-source self-hosted chat UI for model APIs and local models. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.