There is an extension for that
summary
Explains the concrete architecture: an app, an extension and a host app share no direct IPC so communication uses shared containers, UserDefaults or Keychain; the system kills extensions that exceed CPU, memory or launch‑time budgets; dynamic frameworks ease code sharing but noticeably slow startup so many modules favor static linking; widgets must match iOS UX rules and run independently; demos show building extensions that launch within budget and reliably exchange files between app and extension.
AI-written summary · about
chapters (4)
related talks
12mFrom Xcode plugin to Xcode extension
30mA Micro-services perspective on iOS architecture
47mBuilding and Integrating Frameworks
39mScaling iOS DevX with Tuist
45mSwift, Frameworks & Modules, Learnings from CocoaPods
29mThe new Era of No-code/Low-code -Why and how to open your platform for external dev
43mBuilding iOS Apps without Xcode
44mMake your project great again