Built-in property wrappers (@State, @Published) in Swift

Introduction

Property wrappers like @State and @Published help you keep track of data that can change. They automatically update your app's screen when the data changes.

When you want to update the user interface after a user changes a value, like toggling a switch.

When you want to share data between parts of your app and update views automatically.

When you want to keep a simple piece of data inside a view that changes over time.

When you want to notify other parts of your app about data changes.

Syntax

Swift

import SwiftUI

struct ContentView: View {
    @State private var count: Int = 0

    var body: some View {
        Button("Tap count: \(count)") {
            count += 1
        }
    }
}

class Model: ObservableObject {
    @Published var name: String = ""
}

@State is used inside SwiftUI views to hold simple, local state.

@Published is used inside classes that conform to ObservableObject to notify views when data changes.

Examples

Example with @State holding a number inside a view.

Swift

struct CounterView: View {
    @State private var count: Int = 0

    var body: some View {
        Text("Count is \(count)")
    }
}

Example with @Published inside a class to notify changes.

Swift

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

Using @State with a toggle switch to change a boolean value.

Swift

struct EmptyStateView: View {
    @State private var isOn: Bool = false

    var body: some View {
        Toggle("Switch", isOn: $isOn)
    }
}

Simple @Published property in a model class.

Swift

class SingleValueModel: ObservableObject {
    @Published var value: Int = 0
}

Sample Program

This program shows how @State keeps track of a local number inside the view, and @Published updates the user name in a shared data model. Pressing buttons changes the values and updates the screen automatically.

Swift

import SwiftUI

class UserData: ObservableObject {
    @Published var name: String = "Alice"
}

struct ContentView: View {
    @State private var localCount: Int = 0
    @ObservedObject var userData = UserData()

    var body: some View {
        VStack(spacing: 20) {
            Text("Local count: \(localCount)")
            Button("Increment Local Count") {
                localCount += 1
            }
            Text("User name: \(userData.name)")
            Button("Change User Name") {
                userData.name = "Bob"
            }
        }
        .padding()
    }
}

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

Important Notes

Time complexity: Reading and writing @State and @Published properties is very fast, constant time.

Space complexity: Minimal extra memory is used to store the wrapped values and observers.

Common mistake: Trying to use @State outside of a SwiftUI view or forgetting to mark a class as ObservableObject when using @Published.

Use @State for simple, local state inside views. Use @Published inside shared data models to notify multiple views.

Summary

@State keeps simple, local data inside a SwiftUI view and updates the UI when it changes.

@Published marks properties inside a class to notify views when data changes.

Both help your app stay in sync with data changes without extra code.

Practice

1. What is the main purpose of the @State property wrapper in SwiftUI?

easy

A. To mark properties in a class that notify other objects when changed

B. To create a constant value that never changes

C. To store local, simple data inside a view and update the UI when it changes

D. To handle network requests asynchronously

Solution

1. Step 1: Understand what @State does

   @State is used to keep simple, local data inside a SwiftUI view.

2. Step 2: Recognize its effect on UI

   When the @State data changes, SwiftUI automatically updates the view to reflect the new data.

3. Final Answer:

   To store local, simple data inside a view and update the UI when it changes -> Option C

4. Quick Check:

   @State manages local view data = B [OK]

Hint: Remember: @State is for local view data that changes [OK]

Common Mistakes:

• Confusing @State with @Published
• Thinking @State is for class properties
• Assuming @State handles network or async tasks

2. Which of the following is the correct way to declare a @Published property inside a Swift class?

easy

A. struct MyStruct { @State var count: Int = 0 }

B. struct MyStruct { @Published var count: Int = 0 }

C. class MyClass { @State var count: Int = 0 }

D. class MyClass { @Published var count: Int = 0 }

Solution

1. Step 1: Identify where @Published can be used

   @Published is used inside classes that conform to ObservableObject, not structs.

2. Step 2: Check syntax correctness

   class MyClass { @Published var count: Int = 0 } correctly declares a class with a @Published property and initializes it.

3. Final Answer:

   class MyClass { @Published var count: Int = 0 } -> Option D

4. Quick Check:

   @Published used in classes = A [OK]

Hint: Use @Published only inside classes, not structs [OK]

Common Mistakes:

• Using @Published in structs
• Confusing @State with @Published
• Missing var keyword or initialization

3. Consider the following SwiftUI code snippet:

class Counter: ObservableObject {
    @Published var value = 0
}

struct ContentView: View {
    @StateObject var counter = Counter()
    var body: some View {
        VStack {
            Text("Count: \(counter.value)")
            Button("Increment") {
                counter.value += 1
            }
        }
    }
}

What will be displayed after tapping the "Increment" button twice?

medium

A. Count: 0

B. Count: 2

C. Count: 1

D. Count: 3

Solution

1. Step 1: Understand the initial state

   The Counter class starts with value = 0. The view shows "Count: 0" initially.

2. Step 2: Analyze button action and updates

   Each tap on "Increment" increases counter.value by 1. After two taps, value becomes 2, and the UI updates automatically.

3. Final Answer:

   Count: 2 -> Option B

4. Quick Check:

   2 increments update value to 2 [OK]

Hint: Each button tap adds 1; count updates automatically [OK]

Common Mistakes:

• Forgetting @Published triggers UI update
• Assuming @StateObject resets value
• Counting taps incorrectly

4. Identify the error in this SwiftUI code snippet:

class Model: ObservableObject {
    @Published var text: String
    init() {}
}

struct ViewContent: View {
    @StateObject var model = Model()
    var body: some View {
        Text(model.text)
    }
}

medium

A. Missing initial value for @Published property 'text' in Model

B. Cannot use @StateObject with ObservableObject classes

C. Text view cannot display a String property

D. Model class should be a struct

Solution

1. Step 1: Check property initialization

   The @Published property text is declared but not initialized, and the init() is empty.

2. Step 2: Understand Swift requirement for properties

   All non-optional properties must have an initial value or be initialized in the constructor. Here, text lacks both.

3. Final Answer:

   Missing initial value for @Published property 'text' in Model -> Option A

4. Quick Check:

   Uninitialized property causes error = A [OK]

Hint: Always initialize @Published properties or provide init values [OK]

Common Mistakes:

• Assuming @StateObject can't be used with ObservableObject
• Thinking Text can't display String
• Believing Model must be a struct

5. You want to create a SwiftUI app where a view shows a user's name that can be edited in a separate view. Which combination of property wrappers should you use to ensure the UI updates correctly when the name changes?

hard

A. Use @State in the main view and @Published in a shared ObservableObject class

B. Use @Published in both views

C. Use @State in both views

D. Use @StateObject in the editing view only

Solution

1. Step 1: Understand data sharing between views

   When multiple views need to share and update data, use an ObservableObject class with @Published properties.

2. Step 2: Use @State for local view data and @Published for shared data

   The main view can use @State for local state, but the shared user name should be in a class marked with @Published to notify changes.

3. Final Answer:

   Use @State in the main view and @Published in a shared ObservableObject class -> Option A

4. Quick Check:

   Shared data uses @Published; local uses @State [OK]

Hint: Shared data needs @Published; local view data uses @State [OK]

Common Mistakes:

• Using @State only for shared data
• Using @Published in structs or views directly
• Not using ObservableObject for shared data