Vaadin Blog
One of the biggest changes existing Vaadin users will notice in version 25 is how much simpler the build setup has become.
In Maven-based projects especially, build files now contain far fewer Vaadin-specific configurations. They’re cleaner, easier to read, and less intimidating for newcomers. At the same time, Vaadin 25 improves compatibility with various cloud deployment environments — no more special tricks required.
How to use own Figma components in Vaadin applications
In this guide, you’ll learn how to copy components from Figma and paste them into Vaadin as Java or React code using Vaadin Copilot’s Figma Importer API. This article is based on: Demo project Figma component and instance example Before we begin To have the best experience while working with ...
Upgrading your Add-on to Vaadin 25: A Developer's Guide
Vaadin 25 release is only a couple of weeks away. A traditional issue hindering testing and usage of new major Vaadin versions is add-on compatibility. To help create a quality release, testing and upgrading add-ons is one of the most urgent and helpful ways to contribute to our open-source ...
Introducing the official Vaadin MCP server
We just released our official Vaadin MCP server, a standard Model Context Protocol (MCP) endpoint that lets your AI coding tools query the latest Vaadin docs right from your editor. Plug it into any MCP-compatible client and your AI assistant can pull current component APIs, theming guidance, and ...
Merging Hilla into Flow: practical and strategic changes
We recently announced merging the Hilla framework into the Flow framework. This follow-up gives more detail on what will change in practice for current Vaadin users and where we're heading in the future. Nothing changes for existing applications Support for React remains. We will continue to ...
Merging Hilla into Flow: Embracing the Java core
For more than 25 years, Vaadin has been about one thing: making Java developers more productive while delivering outstanding user experiences. EDIT: Practical and strategic changes highlighted in detail here. Throughout this journey, we’ve evolved our client-side implementation from custom HTML ...
3 Ways to Remove Browser Chrome and Go Fullscreen in Java Web Apps
Imagine your Java web application running without browser toolbars or navigation bars—just pure, focused content filling the entire screen. This guide reveals three proven methods to eliminate browser chrome in Vaadin applications, from zero-code solutions to Progressive Web Apps and the Fullscreen ...
What’s new in Vaadin 24.9
Vaadin 24.9 closes the 24.x chapter with a set of features that smooth out daily workflows and clear the path to what’s next. You can copy-paste designs with your own custom components, manage assets directly with @NpmPackage, and rely on more predictable behavior in routing, forms, and tooltips. ...
What's next for Vaadin 23 users as free support ends?
⚠️ Editor’s note (August 2025): Since this post was published, Vaadin’s plans have changed: Premium is now Team and Ultimate is now Enterprise. The Team plan adds developer support and components, while the Enterprise plan includes long-term maintenance (15 years) and modernization tooling. Polymer ...
How to add HTTPS to your Java web application
HTTPS (aka HTTP over TLS aka HTTP over SSL) is no longer optional for web sites. Even if your application wouldn’t handle critical data that attackers would be interested in, or it would be only used within a secure intranet, modern browsers show a scary “Not secure” warning to users accessing ...