Jared Sinclair🔒 SSL Verified

Table of Contents

• ↓ We Need to Talk About Observation
• ↓ Beware @unchecked Sendable, or Watch Out for Counterintuitive Implicit Actor-Isolation
• ↓ How Do You Know Whether or Not SwiftUI Previews and Preview Content Are Excluded From App Store Builds?
• ↓ Be Careful When You Initialize a State Object
• ↓ Scaled Metric Surprises on iOS & iPadOS
• ↓ Top Alternatives to jaredsinclair.com

6-Month Traffic Trend Estimate

Visual representation extracted from jaredsinclair.com

Content Snippets from jaredsinclair.com

"(Note: Every buzz-and-nonbuzz word of this post was painstakingly conceived and typed by hand using a real-ass keyboard and a real-ass text editor running on my personal computer in my home office outside Cleveland, Ohio. No GPUs were harmed in the making of this film.)"

"For the Impatient of Spirit among you: Apple has effectively deprecated the reigning paradigm of the ObservableObject protocol and @Published properties observed via the Combine framework, but they’ve only partially provided its replacement via the @Observable macro and the withObservationTracking free function. The gaps between the old way and the new way are worth careful consideration."

"Since the advent first of the React framework and then later other similar projects—SwiftUI, Jetpack Compose, etc.—the peppiest and most responsive apps these days are written as thin layers of declarative UI code that spontaneously react to changes in thick layers of object-oriented code. Those latter objects are sometimes called “view models” or “flow coordinators” or whatever you wish to call them. Naming aside, the reactive paradigm on Apple platforms has been reified by SwiftUI. It has usurped UIKit/AppKit as the dominant framework for new UI development."

"What I find most exciting about SwiftUI isn’t just the fact that it’s declarative. What’s most exciting is the other half of my codebase. I’m excited about all the stuff that isn’t SwiftUI. Business logic. View models. UserProviderManagerHamburgerHelper. Files that only have import Foundation at the top and nothing else. That stuff gets written entirely differently in a pure SwiftUI world, relative to how it was written for UIKit/AppKit. In the relatively-before-times, in the kinda-sorta-long-long-ago, there were DataSources and Delegates, IBOutlets and IBActions. Stuff worked like an old telephone switchboard: somebody had to plug the dataSource cable into the SomethingSomethingDataSource jack in a wall of such holes. If anything worked, its because a giant tangle of loosely coupled, weakly-referenced properties got wired up just-in-time."

Key Topics & Focus Areas for jaredsinclair.com:

We Need to Talk About Observation

Beware @unchecked Sendable, or Watch Out for Counterintuitive Implicit Actor-Isolation

How Do You Know Whether or Not SwiftUI Previews and Preview Content Are Excluded From App Store Builds?

Be Careful When You Initialize a State Object

Scaled Metric Surprises on iOS & iPadOS