Bird
Raised Fist0
iOS Swiftmobile~3 mins

Why @Published properties in iOS Swift? - Purpose & Use Cases

Choose your learning style10 modes available
The Big Idea

Discover how a simple tag can make your app update itself like magic!

The Scenario

Imagine you are building an app where you want the screen to update automatically whenever some data changes, like a user's score or a list of messages.

Without any special tools, you have to write extra code to watch for changes and then update the screen manually every time something changes.

The Problem

This manual way is slow and tricky. You might forget to update the screen in some places, causing the app to show old or wrong information.

It's like trying to keep a group chat updated by texting each friend separately instead of using a group chat app.

The Solution

@Published properties in Swift make this easy. When you mark a variable with @Published, Swift automatically watches it for changes.

Whenever the value changes, the app updates the screen or any part that depends on that data without extra code.

Before vs After
✗ Before
var score = 0
func updateScore(newScore: Int) {
  score = newScore
  updateScreen() // must call manually
}
✓ After
@Published var score = 0
// UI updates automatically when score changes
What It Enables

This lets you build apps that react instantly and correctly to data changes, making your app feel smooth and smart.

Real Life Example

Think of a fitness app that shows your step count live. With @Published, the step count on screen updates automatically as you walk, without you needing to refresh anything.

Key Takeaways

@Published properties automatically notify the app when data changes.

This removes the need to write manual update code, reducing errors.

It helps create responsive and user-friendly apps easily.

Practice

(1/5)
1. What is the main purpose of marking a property with @Published in SwiftUI?
easy
A. To make the property constant
B. To make the property private
C. To automatically notify views when the property changes
D. To prevent the property from being saved

Solution

  1. Step 1: Understand @Published role

    @Published marks a property to send updates when its value changes.
  2. Step 2: Connect to UI updates

    This automatic notification helps SwiftUI views update when data changes.
  3. Final Answer:

    To automatically notify views when the property changes -> Option C
  4. Quick Check:

    @Published = automatic update notification [OK]
Hint: Remember: @Published means auto-update UI on change [OK]
Common Mistakes:
  • Thinking @Published makes property private
  • Confusing @Published with constant declaration
  • Assuming @Published saves data permanently
2. Which of the following is the correct way to declare a @Published property inside an ObservableObject class?
easy
A. struct Model: ObservableObject { @Published var count: Int = 0 }
B. class Model: ObservableObject { @Published var count: Int = 0 }
C. class Model { @Published var count: Int = 0 }
D. class Model: ObservableObject { var count: @Published Int = 0 }

Solution

  1. Step 1: Check class and ObservableObject conformance

    @Published must be inside a class conforming to ObservableObject, so class Model: ObservableObject is correct.
  2. Step 2: Verify property declaration syntax

    The correct syntax is @Published var count: Int = 0, not var count: @Published Int.
  3. Final Answer:

    class Model: ObservableObject { @Published var count: Int = 0 } -> Option B
  4. Quick Check:

    Correct syntax = class Model: ObservableObject { @Published var count: Int = 0 } [OK]
Hint: Remember: @Published goes before var inside ObservableObject class [OK]
Common Mistakes:
  • Using struct instead of class for ObservableObject
  • Placing @Published after the type
  • Not conforming class to ObservableObject
3. Given the code below, what will be printed when model.count = 5 is executed?
class Model: ObservableObject {
  @Published var count: Int = 0
}

let model = Model()
model.$count.sink { print("Count changed to \($0)") }
medium
A. Count changed to 5
B. Count changed to 0
C. No output
D. Compile error

Solution

  1. Step 1: Understand @Published publisher

    @Published creates a publisher accessible via $property, here $count, which emits new values on change.
  2. Step 2: Analyze sink subscription and assignment

    The sink closure prints the new value when count changes. Setting model.count = 5 triggers the print with 5.
  3. Final Answer:

    Count changed to 5 -> Option A
  4. Quick Check:

    @Published publishes new values = Count changed to 5 [OK]
Hint: Remember: $property publishes changes, sink prints new value [OK]
Common Mistakes:
  • Expecting output before assignment
  • Confusing $count with count
  • Thinking no output without explicit call
4. Identify the error in this code snippet:
class Model: ObservableObject {
  @Published var name: String

  init() {
    name = ""
  }
}

let model = Model()
model.name = "Alice"
medium
A. Missing initial value for @Published property
B. ObservableObject conformance is missing
C. Cannot assign to @Published property outside class
D. No error, code works fine

Solution

  1. Step 1: Check @Published property initialization

    The property name is initialized in init(), which is valid for non-optional properties.
  2. Step 2: Verify ObservableObject conformance and usage

    Class conforms to ObservableObject and property is assigned outside class, which is allowed.
  3. Final Answer:

    No error, code works fine -> Option A
  4. Quick Check:

    Proper init and conformance = No error, code works fine [OK]
Hint: Remember: @Published properties can be initialized in init() [OK]
Common Mistakes:
  • Assuming @Published needs default value inline
  • Thinking ObservableObject conformance is missing
  • Believing external assignment is disallowed
5. You want to create a SwiftUI app where a @Published property updates a label text automatically. Which of the following is the best way to connect the @Published property to the UI?
hard
A. Use @EnvironmentObject without passing the object
B. Use @State in the view for the property
C. Manually call setNeedsDisplay() after changing the property
D. Use @ObservedObject in the view to watch the ObservableObject

Solution

  1. Step 1: Understand property wrappers for UI updates

    @Published properties notify changes, but the view must observe the object using @ObservedObject to update UI automatically.
  2. Step 2: Evaluate other options

    @State is for local view state, not external objects; setNeedsDisplay() is UIKit, not SwiftUI; @EnvironmentObject requires injection.
  3. Final Answer:

    Use @ObservedObject in the view to watch the ObservableObject -> Option D
  4. Quick Check:

    @Published + @ObservedObject = auto UI update [OK]
Hint: Connect @Published with @ObservedObject in views [OK]
Common Mistakes:
  • Using @State instead of @ObservedObject for external data
  • Trying manual UI refresh calls in SwiftUI
  • Using @EnvironmentObject without proper injection
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard