Vaadin 23, our latest stable release, ships with many cool features and improvements. If your applications are still on Vaadin 14 or earlier, now is the time to consider upgrading to Vaadin 23. Go to our upgrading guide for detailed instructions on how to upgrade your project to Vaadin 23.
Upgrading from Vaadin 14 to Vaadin 23 enables you to leverage a number of new features, including:
- Spring Security helpers that dramatically reduce the amount of boilerplate code required to enable security in Vaadin applications
- Improvements for data binding to Grid that simplify manipulating your data and facilitate binding to Spring Data repositories
- Official Quarkus support
- Official support for Gradle
- Support for the experimental Vite devmode for improved frontend build times
- Improved accessibility and WCAG compliance for all components
- A number of improvements to components APIs, including
- Cell focus event for Grid
- Pattern support for Text Area
- Upload API for clearing file list
- ItemLabelGenerator for RadioButtonGroup and MultiselectListBox
- Improved CRUD configuration API
- A set of CSS utility classes for styling your custom UI elements without writing CSS
- A new Map component (requires Pro subscription)
- Improvements to Vaadin Charts (requires Pro subscription):
- Support for exporting Charts as SVG
- New theme variants
- Java API for Charts styling
- New chart types and other improvements
Vaadin 23 is the latest stable version in our new simplified release model. It will have free support until at least 2024, and commercial support options are available until 2037 (see the roadmap for more details).
To facilitate the process of upgrading to Vaadin 23, we have created a dedicated upgrading guide in the docs. This guide provides a list of the changes required to upgrade a Vaadin 14 application to Vaadin 23. It includes the essential instructions to follow so your project compiles, runs, and behaves in Vaadin 23 as it did in Vaadin 14. The guide also includes a further list of the changes that are recommended to conform with Vaadin 23 best practices and avoid the usage of deprecated APIs and features.