@Published properties in iOS Swift

Introduction

@Published properties help your app update the screen automatically when data changes. This means you don't have to write extra code to refresh the view.

When you want the user interface to change as soon as data changes.

When you have a value that many parts of your app need to watch and react to.

When you want to keep your code simple and avoid manual updates.

When building apps with SwiftUI that need to show live data updates.

Syntax

iOS Swift

class MyModel: ObservableObject {
  @Published var myValue: String = ""
}

The class must conform to ObservableObject to use @Published.

Properties marked with @Published automatically notify views when they change.

Examples

This example creates a counter that updates any view watching count when it changes.

iOS Swift

class Counter: ObservableObject {
  @Published var count: Int = 0
}

Multiple @Published properties can be used in one class to track different pieces of data.

iOS Swift

class UserSettings: ObservableObject {
  @Published var username: String = "Guest"
  @Published var isLoggedIn: Bool = false
}

Even if the initial value is empty, views will update when the property changes later.

iOS Swift

class EmptyModel: ObservableObject {
  @Published var text: String = ""
}

Sample App

This app shows a number that increases every second after you press the button. The @Published property secondsElapsed updates the text automatically.

iOS Swift

import SwiftUI

class TimerModel: ObservableObject {
  @Published var secondsElapsed: Int = 0

  func startTimer() {
    Timer.scheduledTimer(withTimeInterval: 1.0, repeats: true) { [weak self] _ in
      self?.secondsElapsed += 1
    }
  }
}

struct ContentView: View {
  @StateObject private var timerModel = TimerModel()

  var body: some View {
    VStack {
      Text("Seconds: \(timerModel.secondsElapsed)")
        .font(.largeTitle)
        .padding()
      Button("Start Timer") {
        timerModel.startTimer()
      }
      .padding()
    }
  }
}

@main
struct MyApp: App {
  var body: some Scene {
    WindowGroup {
      ContentView()
    }
  }
}

Important Notes

Time complexity: Updating a @Published property is very fast, just a simple value change.

Space complexity: Minimal extra memory is used for the publisher behind the scenes.

Common mistake: Forgetting to mark the class as ObservableObject or forgetting to use @StateObject or @ObservedObject in the view to watch the changes.

Use @Published when you want automatic UI updates. Use manual updates only if you need more control.

Summary

@Published makes properties send updates automatically.

Use it inside classes that conform to ObservableObject.

It helps keep your UI in sync with your data easily.

Practice

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