What’s new with FDC3 v2.0?
summary
FDC3 2.0 adds concrete plumbing: transactions and streaming channels let an intent return deferred results or a private channel for CRUD and feed workflows; channels gain lifecycle and privacy rules. APIs standardize on unique app ids, async calls and clearer errors; apps can target specific instances and carry metadata. The revamped app directory with vendor-agnostic manifests, localization and interop descriptors supports multiple desktop agents. Community uptake is real — npm saw 500 downloads in a day — and work on bridging agents and new context types continues.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:42FDC3 2.0 DRAFT Specification is out!
- 4:53Growing Momentum
- 9:32FDC3 History
- 13:21Release Highlights
- 15:45Forming Discussion Groups
- 16:57Crossing the Chasm
- 18:20Desktop Agent API
- 24:37App Directory AppDI
- 28:45Context Data & Intents
- 31:53Improving the FDC3 Specifications
- 35:48Existing open issues
- 39:51FDC3 Community page
- 40:49What should FDC3 tackle next?
related talks
36mReal Life Use Cases for FDC3 2.0
33mIntroducing FDC3 Sail, "A Secure Open Source Container for an Open Source Standard"
29mBridging the Gap - Connecting Multiple Desktop Agents in Your FDC3 Environment
29mTaking Channels Async
44mIntro to Firebase Zero to App - Whats new?
40mDependency Management in MFs
07mWhat's new in Firebase | Recap
31mHanami 2: New Framework, New You