Why Built-in property wrappers (@State, @Published) in Swift? - Purpose & Use Cases

The Big Idea

What if your app could update itself instantly without you writing extra code to watch for changes?

The Scenario

Imagine you are building an app where you want to update the screen whenever a user changes a value, like typing in a text box or toggling a switch. Without special tools, you would have to write extra code to watch for changes and then update the screen manually.

The Problem

This manual way is slow and tricky. You might forget to update the screen, causing the app to show old information. It's easy to make mistakes, and the code becomes messy and hard to fix.

The Solution

Built-in property wrappers like @State and @Published automatically watch for changes in your data. When the data changes, they tell the app to update the screen right away. This makes your code cleaner, simpler, and less error-prone.

Before vs After

✗ Before

var name: String = "" // manually update UI when changed

✓ After

@State var name: String = "" // UI updates automatically

What It Enables

They let your app react instantly to data changes, creating smooth and dynamic user experiences without extra effort.

Real Life Example

When a user types in a search box, @State updates the search text, and the app immediately shows matching results without you writing extra update code.

Key Takeaways

@State and @Published automatically track changes in data.

They reduce manual update code and bugs.

They help build interactive, responsive apps easily.