Problems this service addresses
- The developer of a Swing / AWT business app is gone, and no one can fix it
- The app is stuck on Java 8 and security reviews keep flagging it
- Applet / Web Start retirement removed your internal distribution channel
- Every rollout hits trouble from mismatched JRE versions
- You want to move to JavaFX but can’t estimate the blast radius
- You want a new Java desktop app but don’t know how to choose the stack
What we handle here is Java desktop apps running on Windows. The focus is working with the assets you still have and improving them in stages, rather than rebuilding on principle.
Themes we handle well
- New business apps and internal tools built with Swing / JavaFX
- Analysis, feature additions, and bug fixes for existing Swing / AWT apps
- Migrating from Java 8 to Java 17 / 21, including dependency cleanup
- Runtime-bundled exe / MSI distribution with jpackage
- Evaluating and adopting GraalVM native-image for native binaries
- Fixing freezes and stutter around UI threading (EDT / JavaFX Application Thread)
Typical way of working
- First, we organize the app’s structure, Java version, dependencies, distribution method, and pain points.
- Next, we lay out the options — migrate, repair, or keep as is — with costs and risks, and decide the order of work.
- Implementation then covers the build setup, tests, distribution packaging, and logging for operation.
When this is a good fit
- You want to fix an old Java desktop app but don’t know where to start
- You want to combine a Java version upgrade with a rethink of distribution
- You want help choosing between a native Windows app and a Java app, starting from technology selection
- You want one point of contact for a mixed set of .NET and Java internal tools