We’ll cover what’s new in 24.9, revisit the most important highlights from the entire 24.x series, and give a look at our upcoming major release, Vaadin 25.
Updating the full-stack signal integration to be based on the new Java-based signals library that we’ve introduced for Flow. That gives a much richer Java API and interoperability with Flow.
Designing an API that makes it feasible to programmatically create custom “models” for use with e.g. Binder rather than only using models that are automatically generated based on Java types.
Both of these initiatives turned out to take more time than expected. It’s unlikely that they would be ready for the soft feature freeze that we try to stick to for Vaadin 25.0.0.beta1.
I just watched the webinar and I’m looking forward especially to Vaadin 25.
I will soon start building a new application for a customer, and it’s expected to be released mid of next year. I wonder if should start directly with 25-beta1 (being aware that it’s a beta), or start with 24.9. Any advice?
Sounds like it could be useful to start right away with Vaadin 25 in your case since the 25.0.0 release in December should give more than enough time until your release. There’s of course a slightly higher risk of instability still during the beta period but we’re doing our best to avoid those…