Windows development & engineering support from KomuraSoft

Java Native App Development & MaintenanceMove your Java desktop app forward.

Development, maintenance and modernization of Swing, AWT and JavaFX applications on Windows. We help assess inherited software, migrate Java versions and simplify deployment.

No specification document needed. Start with what you know.

  • Work directly with an engineer
  • Start before requirements are finalized
  • Commission only the scope you need

You do not need a finished specification

Start with the problem you need to solve.

You need to fix a Swing application without its original developer

We examine the source, libraries and development environment to establish what can be changed.

You need a Java upgrade, but the impact is unclear

We review dependencies and operating conditions, then select and validate a suitable migration target.

Different runtime setups make deployment difficult

We consider distribution with a bundled runtime and document the installation process.

Discuss the technical details with the engineer doing the work.

Profile photo of Go Komura

Founder & engineer

Go Komura

A Windows-focused engineer works with you from the initial discussion through investigation, design and implementation. You do not need to have every technical detail worked out before getting in touch.

Experience & technologies / Company information

Before you commission work

Know who you will be working with.

Our company details, location and founder's experience are available to review. We confirm the work we can take on after discussing your application and environment.

About KomuraSoft

Scope of support

A focused task or a complete application.

From a specific investigation or change to end-to-end development, we agree on a scope that fits your situation.

New Java desktop applications

Develop business applications, device integration software and internal tools with Swing or JavaFX. From JPY 500,000.

Existing Java application maintenance

Assess, extend and repair Swing, AWT and JavaFX applications, including maintenance handover.

Java version migration

Assess environments such as Java 8 and their dependencies, select a migration target and validate compatibility.

Windows packaging and distribution

Package an application with its runtime as an exe or MSI using jpackage, and assess whether GraalVM native-image is applicable.

Examples of results and deliverables

  • Existing assets and dependencies and migration approach
  • Developed or updated software and validation results
  • Build and packaging and deployment instructions

These are examples, depending on the work commissioned. We agree on the scope and format of deliverables when preparing the estimate.

Facing a similar challenge? Tell us where things stand.

No specification document needed. Start with what you know.

Pricing and process

You do not need every detail decided to get started.

Start with the code, build and deployment setup

Commission a new application, or begin with an assessment, a bug fix or a migration plan for an existing one.

Pricing guide

New development from JPY 500,000

Pricing depends on project size. Assessment, changes and maintenance of existing applications are quoted separately for the agreed scope.

Initial feasibility checks and paid engagements

Initial checks needed to assess feasibility and prepare an estimate are generally free, on the understanding that you will commission the full development if it is found feasible. Extended validation, dedicated environments, prototypes, proofs of concept and detailed investigation reports may require a paid engagement.

An investigation or review commissioned in its own right is quoted as a separate paid service. We explain the scope and cost before any paid work begins.

  1. Tell us about the situation

    Share your goal, the problem and the environment, as far as you know them.

  2. Review the scope and cost

    We outline the investigation needed, scope, deliverables, cost and proposed process.

  3. Agree before work begins

    During the work, we share progress, confirmed findings and remaining constraints.

  4. Review the results and handover

    We validate the results under agreed conditions and prepare for deployment or the next step.

Need more technical detail?

Explore technologies and the detailed approach

Support your Java business application through maintenance and deployment.

Take over a Swing application after its developer has left. Upgrade Java. Reduce differences between runtime environments at deployment sites. KomuraSoft supports the development, modification and maintenance of Java desktop applications on Windows. New development starts at JPY 500,000, with an estimate based on the agreed scope.

This service covers desktop applications using Swing, AWT and JavaFX. We choose an approach that fits the existing software and operations, rather than assuming a rewrite or native compilation.

Challenges we can help with

  • Features and fixes are blocked because nobody understands the existing app.
  • The impact of moving from Java 8 or another old environment is unclear.
  • An Applet or Web Start distribution method needs to be replaced.
  • Differences in JREs and settings cause installation problems.
  • A Swing-to-JavaFX migration, UI freeze or stuttering display needs attention.
  • You need to choose between Java and another Windows development technology.

Development and maintenance we support

New applications and existing code

We develop Swing or JavaFX business applications and internal tools, and investigate, extend and repair existing Swing, AWT and JavaFX code. We review UI and background-thread responsibilities, responsiveness and logging.

Java and dependency updates

We check the current Java version, build setup, libraries and operating conditions. The work includes compatibility checks, testing and deployment procedures—not just selecting a newer version.

Distribution improvements

We consider exe or MSI distribution with a bundled runtime using jpackage, clarifying the preparation and settings needed at installation sites. GraalVM native-image is assessed separately for dependency support and build constraints. Bundling a runtime and compiling a native executable are different approaches; the choice follows the goal.

How an engagement proceeds

  1. Assess the current setup. Review the source, Java version, libraries, build and distribution methods.
  2. Compare approaches. Clarify the scope and risks of continued maintenance, targeted changes, version migration and replacement.
  3. Implement and validate. Test the agreed functions and environments, then prepare distribution instructions and logs.

We also support discussions involving a mix of .NET and Java tools on Windows. Tell us what the application does and why you are considering changes or migration.

Questions before commissioning work

Can you help with a Java app whose developer is no longer available?

Yes. We examine the source, development environment and dependencies before making changes or taking on maintenance. When some assets are missing, we start by identifying what remains and what needs further investigation.

Should we upgrade an application that still uses Java 8?

We do not recommend an upgrade automatically. We review the JDK support arrangements, security requirements, dependencies and expected operating life. Potential targets include Java 17 or 21, selected according to compatibility and maintenance conditions.

Can users install the application without installing a JRE separately?

We can consider exe or MSI distribution with a bundled runtime using jpackage. Native compilation with GraalVM native-image is a separate approach; its applicability depends on validating the UI and library dependencies.

Should we keep the Java app or rebuild it with a different technology?

We compare device integration, local file and hardware access, existing assets and maintenance arrangements. We explain the reasons to keep a desktop application alongside the benefits and effort of replacement, and can plan a phased migration where appropriate.

Get in touch

A few lines about your situation are enough.

You do not need a detailed specification or technical terminology. Share what you know about:

  • The problem or the outcome you need
  • The software, devices and operating environment
  • Your preferred timeframe, even if it is not decided

There is no need to send confidential documents or passwords with your initial inquiry.

Example inquiry

We have inherited an old Swing application. We would like help updating Java and changing the distribution method so that users can install it more easily.

No specification document needed. Start with what you know.

The discussion button opens our English contact page with ways to get in touch. “Send an email” opens a draft with the service name and blank prompts for your inquiry.