Java teams maintaining legacy Swing or JavaFX desktop applications face a critical decision in 2026: keep the desktop UI, migrate to the browser, modernize incrementally, or rewrite. The right answer depends on runtime environment, deployment needs, user access patterns, and test coverage rather than framework popularity. Desktop still makes sense for local device access, multi-window workflows, and controlled workstations. Browser-based modernization is better when users need cross-device access, centralized deployment, faster updates, and improved accessibility. Full rewrites carry high risk for business-critical systems with undocumented behavior embedded in UI event handlers. A staged approach is recommended: map workflows, separate business logic from UI, add tests, use tools like Vaadin's SwingBridge to enable browser access first, then replace screens incrementally. Vaadin Flow is positioned as a way to build browser UIs in server-side Java without introducing a separate JavaScript frontend stack.
