# Complete Guide to io.Connect Integration Mechanisms

**URL:** https://community.interop.io/t/complete-guide-to-io-connect-integration-mechanisms/538
**Category:** io.Connect Desktop
**Tags:** Knowledge-base
**Created:** [June 17, 2026, 2:11pm UTC](https://community.interop.io/t/complete-guide-to-io-connect-integration-mechanisms/538 "2026-06-17T14:11:23Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)
#### Post date: [June 17, 2026, 2:11pm UTC](https://community.interop.io/t/complete-guide-to-io-connect-integration-mechanisms/538/1 "2026-06-17T14:11:23Z")

</div>

io.Connect is a real-time UI integration platform that allows multiple apps (web, native, in-house and 3rd party) to interact at the user interface level. Instead of siloed applications, developers can use io.Connect’s APIs to enable seamless cross-application workflows – delivering _“intuitive paths from one function to the next”_ and reducing the need for manual copy-paste between apps. The platform injects a common integration layer (io APIs) into applications, enabling features like shared data contexts, cross-app method calls and coordinated window management.

> There are two variants of the io.Connect Platform; io.Connect Desktop and io.Connect Browser, they share a common functional foundation. The Web application capabilities of the two editions are functionally equivalent, io.Connect Desktop provides additional support for non Web based applications. Io.Connect Desktop is installed on the desktop as a Windows or macOS application, io.Connect Browser is a zero-install browser-based platform.

This series is based on Martyn Bedford’s Developer Guide and Georgi Georgiev’s work on every io.Connect Desktop communication pattern

> **[View the original slide deck on every io.Connect Desktop communication pattern and exactly when to use each one.](https://data-sharing-deck.vercel.app/)** by Georgi Georgiev.

https://data-sharing-deck.vercel.app/
## A Drill Down

Below are articles you can reference when thinking through the architecture and building your interop architecture.

| Section | Description |
| --- | --- |
| **[Foundation](https://community.interop.io/t/io-connect-desktop-for-developers-the-big-picture/567)** | Gateway architecture, WebSockets, interop clients & servers - the plumbing that powers everything |
| **[App-to-App Communication in io.Connect: Practical Guidance](https://community.interop.io/t/app-to-app-communication-in-io-connect-practical-guidance/553)** | Each mechanism: when to use, when to avoid, code samples, and flow diagrams |
| **[Key io.Connect Integration Concepts](https://community.interop.io/t/key-io-connect-integration-concepts-explained/255)** | A conceptual overview of integration mechanisms with business use cases |
| **[Data Sharing Comparison Cheatsheet](https://community.interop.io/t/io-connect-data-sharing-comparison-cheatsheet/324)** | A feature-by-feature comparison matrix and per-mechanism cheatsheet |
| **[When to Use What](https://community.interop.io/t/io-connect-patterns-and-apis-making-the-right-choice/570)** | Patterns, real-world scenarios, and a decision flowchart |

**How to Use This Guide**

If you’re new to io.Connect, start with the _Foundation_ and _Key Concepts_ articles. They’re useful not only for developers, but also for UX designers, product managers, and anyone who wants to understand how the platform works.

If you’re building something, jump straight to _When to Use What_ and the _Comparison Cheatsheet_ - they’ll help you make decisions quickly.

And if you’re implementing a specific workflow, use the _Practical Guidance_ article as your reference for concrete patterns and trade-offs.

---

_[View the full topic](https://community.interop.io/t/complete-guide-to-io-connect-integration-mechanisms/538)._