Legacy desktop apps hinders your digital progress
Economies of scale in the cloud
Agility to innovate by integrating with latest technologies
Ease of upgrading your own product
Your customers expect web-enablement
Swing’s technical relevance is eroding
- The shift from desktop to mobile caused the end for the desktop-only era. As the demand decreased, the supply for desktop development skills, crucial for Swing applications, has diminished.
- With Swing, there’s a lack of responsiveness on different platforms – in both the application performance and their development.
- In 1999, a Swing application could work on almost any graphics-enabled computing device without having to be recompiled. Nowadays less than half of devices sold are able to run Swing.
- By staying with Swing, your IT infrastructure becomes complex and costly to maintain.
No more plugins nor JRE installations
Unlock mobile use
Improve your user experience
Build with UI components
Clock ticking loudly for Swing and SWT users
Tools to Migrate Swing Applications to Web - Part 1
Tools to Migrate Swing Applications to Web - Part 2
Procountor made a UX-first accounting software with Vaadin
When Apple dropped support for their own JVM, we had to start supporting a Swing version of our app as well. The abstraction layer made it a natural choice for us to do the same with Vaadin, knowing that the API was so similar to both Swing and AWT. And that's what we did. Quite successfully I might add.