See what desktop application modernisation looks like in practice. Pavel uses Webswing AIM to update a search screen and the main navigation in BlueSeer, then shows the new and original screens running together.
See what desktop application modernisation looks like in practice. Pavel uses Webswing AIM to update a search screen and the main navigation in BlueSeer, then shows the new and original screens running together.
You can start modernising a desktop application with one screen your users rely on. In this recorded demo, Martin Balaz talks to Pavel Chudomel, who leads the development of AIM (AI Modernisation with Webswing). Pavel uses BlueSeer, an open source Java Swing application, to show how a new web interface can work with the existing application logic while other screens stay in use.
What you’ll see
- From source code to a project map. Pavel opens the BlueSeer source in AIM and shows how the canvas maps the application’s screens. He explains how shared components give later screens a consistent look.
- A search screen that works in the browser. Pavel starts the migration of API Browse. One agent makes the changes and another reviews them. Pavel then opens the new interface in Webswing and runs a search using the existing application logic.
- New navigation alongside the original screens. Pavel asks AIM in chat to migrate the main navigation. He uses the updated header to return to API Browse, then marks that screen as finished on the project canvas.
Three questions from the demo
Why use AIM on a large application? The more screens share the same patterns, the more places you can reuse the components and design decisions you’ve already made. What your team builds for the first few screens gives it a starting point for the next ones.
What does AIM add if your team already uses Codex or Claude Code? AIM gives the coding agent context for the selected screen, sets boundaries on what it can change and coordinates review. The goal is behavioural equivalence. If a user runs the same search through the new interface, the application should return the same results. The team can check that in the running application.
Can we run it on our own infrastructure? Pavel discusses an on-premises setup where the AI model runs on infrastructure managed by your team. The setup depends on where the model runs and what source code it needs to process.
Where could you start with your application?
Think of a desktop workflow that would benefit from a clearer web interface. How you connect that interface to the existing application depends on its technology and architecture. For more on how AIM approaches screen-by-screen modernisation, read our introduction to AIM.
AIM is currently in preview, with a public release planned for 2027. Tell us what your desktop application runs on and which workflow you’d like to modernise first. Let’s talk about your application.
