Bridging Combine into SwiftUI
Feed publisher output into observable state.
Bridging Combine into SwiftUI is a free SwiftUI Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the SwiftUI Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Two Worlds to Connect
Combine produces a stream of values over time, while SwiftUI redraws from state. Bridging the two means feeding that stream into state.
State Drives the UI
SwiftUI only re-renders when an observed property changes, so to update the screen a publisher must ultimately write into such a property.
Assign into a Property
The assign subscriber writes each value straight into a property using a key path, no closure needed.
publisher
.assign(to: &model.$results)Observable Models Hold State
Put your published properties in an @Observable model class, then let Combine update them as values arrive.
@Observable
class SearchModel {
var results: [String] = []
}Store Your Cancellables
Keep subscriptions alive by storing each cancellable in a set that lives as long as the model.
private var bag = Set<AnyCancellable>()Sink Then Update
In a sink, assign the received value to a state property, and SwiftUI redraws on the next run loop.
pub.sink { [weak self] value in
self?.results = value
}.store(in: &bag)Stay on the Main Thread
UI updates must happen on the main thread, so use receive(on:) before delivering values to state.
.receive(on: RunLoop.main)Driving from TextField
Bind a TextField to a model property, then publish its changes so a Combine pipeline can react to typing.
TextField("Search", text: $model.query)Avoid Retain Cycles
Capture self weakly inside sink closures so the model is not kept alive by its own subscription.
sink { [weak self] v in self?.value = v }Combine Plus async/await
Modern code often pairs Combine for input with async/await for the network call inside the pipeline.
A Clean Bridge
The pattern is steady: publisher to operators to sink or assign, landing values in observable state. 🌉
Quick Check
You feed a Combine publisher into an @Observable model from a background thread. The UI flickers oddly. What is the fix?
Recap: Stream to Screen
You connected Combine to SwiftUI: pipe values through operators, hop to the main thread, and land them in observable state. 🎉
Frequently asked questions
Is the “Bridging Combine into SwiftUI” lesson free?
Yes — the full text of “Bridging Combine into SwiftUI” is free to read here on the web, and the SwiftUI Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the SwiftUI Academy course, upgrade to CoddyKit PRO.
What will I learn in “Bridging Combine into SwiftUI”?
Feed publisher output into observable state. You practise SwiftUI Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start SwiftUI Academy?
No prior experience is required. SwiftUI Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Bridging Combine into SwiftUI” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this SwiftUI Academy lesson?
Yes. Every SwiftUI Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Publishers & Subscribers
- Transforming with map & filter
- Debounce for Live Search
- Bridging Combine into SwiftUI