
Electron vs .NET MAUI vs GTK for desktop engineering tools
How to choose between Electron, .NET MAUI and GTK when building desktop tools for embedded, industrial and technical workflows.
02 / SOFTWARE
Desktop applications and engineering tools for the client’s operating systems, connecting devices, data and operations within the required stack and distribution practices.
Platforms and tools follow your context. Some examples:
Software
Tools for operating systems, devices and users
Qt / QML · .NET · other stacksFit with the client environment
C++ · Python · C#Modules and responsibilities
Serial · USB · networkingAcquisition and control
Files · databases · exportsImport and reporting workflows
Packages · installation · versionsAgreed environments and releases
Tests · diagnostics · updatesSoftware evolution
The technologies shown are examples.
Engineering support within your team, with shared tools and working methods.
TECHNICAL SCOPE
I work within your existing stack or we agree technologies for new development. Operating systems, libraries, peripherals and distribution guide the choices. I separate interface, logic and device access to keep the application responsive, checking workflows against real daily tasks.
I clarify supported operating systems and versions, installation, updates and tools the application must integrate. I can contribute to existing modules and interfaces using the team’s repositories, libraries and conventions, or start new development from agreed requirements.
For a device-connected tool, tests can cover connection, acquisition, operation cancellation and recovery after disconnection. Long processing and communication should leave users with understandable status; errors and produced data remain traceable.
Application, sources, build and installation instructions, formats and test cases. Acceptance covers supported operating systems, expected peripherals and behaviour with errors or invalid data.
Describe users, operating systems, peripherals, existing formats and one complete operation to simplify.
Work starts from the build, sources and current behaviour. Scope can cover a feature, peripheral, fix or integration while retaining the client’s review process.
THE NEXT STEP