# FDC3 Context vs. Intent: What’s the Difference?

**URL:** <https://community.interop.io/t/fdc3-context-vs-intent-what-s-the-difference/56>\
**Category:** io.Connect Desktop\
**Tags:** FDC3, FAQs\
**Created:** [August 6, 2025, 9:00pm UTC](https://community.interop.io/t/fdc3-context-vs-intent-what-s-the-difference/56 "2025-08-06T21:00:00Z")\
**Posts on this page:** 1\
**Page:** 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:** [August 6, 2025, 9:00pm UTC](https://community.interop.io/t/fdc3-context-vs-intent-what-s-the-difference/56/1 "2025-08-06T21:00:00Z")

</div>

This is one of the most common points of confusion for developers new to FDC3:

- **Context:** Think of this as a shared state. When your app broadcasts a `Context` (like an instrument ticker), it’s sharing that information with _every other app on the same channel_. It’s a one-to-many communication model designed to keep everything in sync.
- **Intent:** This is more like a direct command. When you raise an `Intent` (like `ViewChart`), you’re asking the FDC3 Desktop Agent to find _one specific app_ that can handle that action and send it the relevant data. It’s a one-to-one communication model designed to trigger a specific workflow.