Vaadin is AI native. And it's an amazing fit for Spec-Driven Development. Vaadin 25.3 is built for AI coding agents that work on Java UIs: ✅ A dev loop that works like an IDE for your agent ✅ A self-hosted MCP server with the full Java API (even air-gapped) ✅ Browserless tests, so the agent gets fast feedback without a browser ✅ An Observability Kit insights endpoint your agent can read Why does this matter for Spec-Driven Development? With Vaadin, the UI is plain Java. No JavaScript, no REST layer, no second tech stack. The agent works in one language and one codebase. That makes it much easier to go from the spec to running code, and to check with tests that the code still matches the spec. Specs give the direction. Vaadin keeps the path short. 🎥 Watch the 5-minute overview: youtube.com/watch?v=WnkI6xA9… 📣 Want to see it live? Next week I speak at Vaadin Create 2026 in Barcelona (27-28 October): "Spec-Driven Development - Why Vaadin Is the Perfect Fit" AI can generate code. The hard part is to keep it aligned with the system you really want to build. I will show how specifications and architectural guardrails guide a full-stack Java application while it grows. See you in Barcelona! 🇪🇸 vaadin.com/vaadin-create-202… #Vaadin #Java #SpecDrivenDevelopment #AIUP #AI #VaadinCreate

How fast can your AI agent find out that the code it just wrote is correct? This question matters more than ever. Agents write code in seconds, but browser-based tests take minutes and often fail for the wrong reasons: timing, waits, flaky selectors. Vaadin Browserless Testing changes this. The whole flow runs in one JVM: the view, the validation, the service, the jOOQ query. Tests run in milliseconds and are deterministic. When a test fails, the code is wrong. Not the timing, not the network. Bonus: JaCoCo sees the UI code too, so you get one honest coverage number for the entire application. In my new blog post I explain why this is a game changer for AI generated web applications, and why the classic SPA architecture cannot match it: martinelli.ch/why-vaadin-bro… #Vaadin #Java #SpringBoot #jOOQ #Testing #AI

A small experiment with Claude Code: Hotel room search, built twice. 1) Vaadin + Spring Boot + jOOQ + Testcontainers + PostgreSQL: 3 minutes. 2) Angular + Python + DynamoDB: about 5x longer. Why the gap? One stack is one language, one runtime, and a clear data model. The other is two ecosystems, two languages, and design decisions that need to be made up front. Choose your tech stack wisely.