The image-first flow

The claim is stated with a designer in the room: “yo hoy en día siento que Figma está en el pasado… el 90% de la gente que utiliza Figma ya no necesita utilizar Figma” ▸ 17:13, and Julia, the UX designer, agrees, adding their own confession: every Figma project of theirs died inside Figma, mockups that never shipped. The corollary raises stakes: with a little practice, UI/UX designers “están capacitados para ser diseñadores y frontend” ▸ 17:56.

The receipts are Severo’s actual screens. Every view, login, the three-button menu, the exercises window, was iterated as an image in Nano Banana, one instruction per turn, because batching them does nothing: “ponga la casita… arrégleme el gráfico estaqueado… quíteme la leyenda del heatmap… estíreme la actividad hasta el otro lado” ▸ 20:07, down to color-coding the vocabulary grid by learning state. Then the handoff: give Gemini 2.5 Pro the finished image plus the theme file, “hágame la UI de analítica”, and the Flutter comes back “casi que perfecto, a la primera”, leaving only font sizes ▸ 22:09. Even Figma’s last moat, the plugin packs of icons, falls: Gemini writes a clean SVG logo in three lines of code ▸ 23:12.

itera en imagen, congela, traduce a código: el mockup ya no es un documento, es el borrador del build →

Why image-first beats straight-to-code (the Stitch flow): pixels are cheaper to argue with, “tú la puedes manipular muy rápido” ▸ 26:38, and the real bottleneck was never tooling: “lo difícil es visualizar las cosas. Cuando tú ya las visualizas, fluye” ▸ 25:19. The winning pipeline, named for the record: work the image until it’s right, then translate it to code ▸ 27:00. Wireframes survive as an optional on-ramp; Canva survives for now (“el día que el texto salga 100% perfecto, ya tampoco”); Figma, in this house, is a museum…