io.Connect Desktop 10.0 introduced a major upgrade in the way you can now build and customize io.Connect Desktop installers. We’re moving from the old model, where our team at interop.io built per-client installers, to a new, self-serve Seed Project model, powered by an easy-to-use CLI tool.
Why We’re Making the Change
Until now, every io.Connect Desktop installer was handcrafted by the interop.io team. You had to send us the configuration and branding, we put together the build, ran validations, signed it, and delivered the package to you. It worked, but the process was inefficient. Even tiny tweaks could take time. The model didn’t support macOS, and automated testing in your environment was limited
The new model turns all of that around. Now you can generate your own installers from a Seed Project created with the new io.Connect CLI. This change brings flexibility, increases speed, and lets you move at your own pace.
How the Seed Project io.Connect CLI Works
With the new io.Connect CLI, you can generate a baseline project that includes the components and configurations you are licensed to use. The CLI instantly creates a ready-to-customize starter repository - the Seed Project.
From there, you can use version control on your own repositories, apply your own branding/configurations, and extend it as you need. You can write automated tests that reflect your own environment and plug in straight into your existing CI/CD pipelines.
With the Seed Project, customizing your deployment is straightforward. You can easily tailor the look and feel of your platform, update assets such as icons, texts and modify the workspace applications. This is all done by editing your project in your preferred development environment, like Visual Studio Code. Any changes you make are immediately reflected in your next build, giving you complete control over your product’s appearance, assets, and functionality.
When everything is ready, use your internally approved pipeline process to package and sign your own installer or ZIP package using your company’s keys.
You can use the new Default Platform Mode to create an OS-independent package (running on both Windows and macOS) or the Advanced Platform Mode (Windows-only) if your users require advanced capabilities like visual integration of native applications.
What’s Different for You
The biggest improvement is ownership and speed. You no longer submit packaging requests or wait for delivery. Instead, you create and manage your own installers directly, whenever you want. The new model enables on-demand installer generation via the CLI and gives you full control of your assets, configurations, and releases.
You also gain flexibility. Because your configuration and build scripts live in your own repository, you can make changes, review them through pull requests, and track every version through your own CI/CD process. Automated testing is built right in - you can set up your pipeline so that installers are only created if your tests pass, ensuring reliability and consistency.
The new process also supports Auto Updates for your EXE (Windows) and DMG (macOS) installers. You can host your own update servers, giving you full control over how and when updates reach your users.
Getting Started
Excited to try it? Here’s how to get started:
-
Check the upgrading to 10.0 guide
-
Speak to your Client Success Manager if you have any concerns or post your questions in the Community
-
Check out the io.Connect 10 technical session recording (login with a customer account to access assets)