# Io.Connect Desktop on macOS **URL:** \ **Category:** io.Connect Desktop\ **Tags:** Knowledge-base, macOS, iocd-10\ **Created:** [December 9, 2025, 11:25am UTC](https://community.interop.io/t/io-connect-desktop-on-macos/406 "2025-12-09T11:25:25Z")\ **Posts on this page:** 1\ **Page:** 1
**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:** [December 9, 2025, 11:25am UTC](https://community.interop.io/t/io-connect-desktop-on-macos/406/1 "2025-12-09T11:25:25Z")
With the release of [io.Connect Desktop 10.0](https://docs.interop.io/desktop/getting-started/changelog/10-0/index.html) Mac users can finally get the desktop experience, complete with multi-window layouts, notifications, app management, and key interoperability capabilities that make io.Connect Desktop so powerful. This will let: - Developers build and test interop-enabled apps on macOS - Firms running mixed environments (Windows + Mac) achieve a consistent experience across teams with the same shared contexts, workflows and tools. - Ops and product teams roll out io.Connect Desktop firm-wide, no matter what OS end-users prefer. ## io.Connect Desktop on macOS specifics io.Connect Desktop on macOS supports most of the [capabilities](https://docs.interop.io/desktop/capabilities/launcher/index.html) offered by io.Connect Desktop on Windows with a few OS-related [limitations and specifics](https://docs.interop.io/desktop/developers/macos-support/index.html#os_limitations). If you’re already using the product, there’s no additional learning curve. ### Layouts and Workspaces Layouts and Workspaces for web apps work on macOS using the same configuration as on Windows (no changes needed to workspace definitions), because the default platform mode is OS-independent and supports the same web-based window management model. Data integration with Desktop apps installed on macOS is possible if appropriate SDKs/language bindings exist (and the respective technology is supported on macOS). You can find the list of client libraries on the documentation page [here](https://docs.interop.io/desktop/getting-started/how-to/interop-enable-your-apps/overview/index.html#overview). > **Note:** > > Desktop apps installed on macOS (not web apps) cannot participate visually in Groups, Layouts, or Workspaces. Visual integration of native apps is not supported, but io.Connect Desktop on macOS can launch native apps. You can still do data integration (e.g. share context) with applications running on macOS e.g. Java apps and “talk” to them. ### Application Adapters Microsoft Office Adapters, Bloomberg Adapter, and Fidessa Adapter aren’t available for macOS ### Visuals io.Connect Desktop on macOS does not support non-rectangular groups. Groups with irregular shapes will be turned into groups with rectangular share, using background to cover the gap. The only supported icon file type on macOS is PNG. Settings and programmatic operations related to Windows taskbar icons and Windows taskbar titles aren’t available on macOS because the macOS Dock displays only a single icon for an app irrespective of how many processes or windows it has opened Windows will not snap to the edges of the screen when dragged. **[Full list of functionalities and limitations when using macOS](https://docs.interop.io/desktop/developers/configuration/system/index.html#platform_modes-default)** (see the Default Platform mode section in the docs) ## Questions and answers ### Migration **Question:** Do I need to rewrite apps/platform settings? **Answer:** No, io.Connect Desktop and your interop-enabled web apps don’t require special configuration to be able run on mac OS. * * * ### Delivery **Question** **:** How is it delivered? **Answer:** You can retrieve, configure, and package the application by creating a **[seed project](https://community.interop.io/t/io-connect-seed-project-via-cli-enabling-you-to-build-your-own-installers/405/1)** via the io.Connect CLI. * * * ### Developer tools **Question:** Can I use the **Developer tools** on Mac? **Answer:** Yes, you can use the Interop Viewer and Context Viewer on macOS just like on Windows. * * * ### macOS version **Question:** What macOS versions does io.Connect Desktop run on? **Answer:** Same as Electron/Chromium macOS requirements. Currently: - **Supported macOS Versions** **:** macOS 15 Sequoia or later - **CPU:** Apple Silicon M1 or later * * * ### Disk space **Question:** How much disk space does io.Connect Desktop need? **Answer:** SSD with at least 3 GB of free disk space * * * ### Memory **Question:** How much memory (RAM) is required? **Answer:** 16 GB RAM or more * * * ### io.Bridge **Question:** Is io.Bridge compatible across Windows, macOS, and the browser? **Answer:** Yes, io.Bridge is a server-side component, thus it is agnostic of OS, so when hosted, io.Bridge will work between io.Connect Desktop on Windows, io.Connect Desktop on macOS, and io.Connect Browser. * * * ### Popups **Question:** Will popups and overlays appear above application windows? **Answer:** Yes. io.Connect Desktop on macOS supports displaying these overlays above application windows, just like on Windows. The only difference is that you may need to double-click to select them. * * * For more details and most up to date requirements check [io.Connect Desktop macOS Support Documentation Page](https://docs.interop.io/desktop/developers/macos-support/index.html). If you have any questions, post them below and we’re happy to answer.