4Soft GmbH, a Munich-based software consultancy, shares how they use Vaadin and Java to build internal engineering tools for a large Volkswagen project. Initially skeptical about Vaadin's longevity, lead architect Rainer Ganß found it practical for Java-focused teams building server-driven internal UIs, support interfaces, and integration tools — particularly where tight Spring ecosystem integration matters. The team avoids recommending Vaadin universally; Angular remains their choice for the main engineering UI with complex client-side requirements. They are currently upgrading to Spring Boot 4 and Vaadin 25, and exploring AI-assisted development workflows.

4m read timeFrom blog.vaadin.com
Post cover image
Table of contents
The CompanyThe Project ContextWhere Vaadin Fits InFrom Skepticism to Practical AdoptionWho Vaadin Is Right ForLooking Ahead
7.1K Impressions