We just put out the summary results of the 2026 Community Survey and I’d love to know what do you think about them - what does resonate with with what doesn’t
Blog post: Vaadin 2026 Community Survey: What Java Developers Told Us | Vaadin
A few things that caught my eye from the Vaadin 2026 Community Survey:
67% of you are building internal applications. Dashboards, admin panels, operational tools are the most common apps. Is that how you feel too, or are you using Vaadin for something else?
35% adopted Vaadin specifically for legacy migration from Swing, JSF, GWT, or JavaFX. If you’ve been through one of these migrations, how did it go? What could have made it go more smoothly?
The most common requests were for more component, better documentation and compatibility with React. We’re taking all three seriously. But I’m curious: if you could only choose one improvement for us to focus on right now, what would it be?
A few things also made us question what we thought we knew. A lot of newer developers didn’t know that Vaadin’s core is open source (Apache 2.0). And features like Copilot and Acceleration Kits didn’t seem to be as valuable as we thought they would be.
This is the place to dig into this topic further, whether you filled survey out or not. To get things started, here are a few questions:
- What is one thing about Vaadin that you like and don’t want us to change?
- What’s your biggest day-to-day frustration?
- If you’ve migrated from a legacy framework, what surprised you most about the process?
Looking forward to hearing from you!