{"id":52332,"date":"2026-06-19T15:43:37","date_gmt":"2026-06-19T19:43:37","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=52332"},"modified":"2026-06-19T15:44:53","modified_gmt":"2026-06-19T19:44:53","slug":"swiftui-in-appleos-27","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/06\/19\/swiftui-in-appleos-27\/","title":{"rendered":"SwiftUI in appleOS 27"},"content":{"rendered":"

macOS Golden Gate 27 Beta Release Notes<\/a>:<\/p>\n

\n

AsyncImage<\/code> now automatically caches downloaded images using HTTP caching protocols, allowing servers to control caching behavior via standard headers.<\/p>\n

[…]<\/p>\n

Xcode 27 introduces a new @State<\/code> implementation that avoids this repeated evaluation. This new behavior back-deploys to iOS 17 aligned OSes. The new @State<\/code> is implemented with a Swift macro. It is largely source compatible with the property wrapper version, with a few exceptions.<\/p>\n

[…]<\/p>\n

Text<\/code> views now support TextRenderer<\/code>.<\/p>\n

[…]<\/p>\n

In apps built with the 27.0 SDKs, the new ReadableDocument<\/code> and WritableDocument<\/code> protocols support asynchronous reading and writing, progress reporting, and direct access to document URLs. New DocumentGroup<\/code> initializers that adopt these protocols let you disable document creation for editing-only apps and present custom UI before any document is opened.<\/p>\n

[…]<\/p>\n

TextField<\/code> respects custom font and color styling applied to its prompt.<\/p>\n

[…]<\/p>\n

List<\/code> accepts drops in two cases that previously didn’t work: drags with compatible transfer representations are accepted into reorderable content even when the .reorderableItem<\/code> transfer type isn’t present, and a .dropDestination(…)<\/code> modifier declared on a list item now performs the drop.<\/p>\n<\/blockquote>\n\n

SwiftUI updates<\/a>:<\/p>\n

\n

Build your project in Xcode 27 or later to construct type-agnostic content from closures that you mark with ContentBuilder<\/code><\/a>, which serves as the unified replacement for type-specific builders like ToolbarContentBuilder<\/code><\/a> and CommandsBuilder<\/code><\/a>.<\/p>\n

Add reordering by drag-and-drop in containers such as lists, stacks, grids, or custom layouts with reorderable()<\/code><\/a> and reorderContainer(for:isEnabled:move:)<\/code><\/a>.<\/p>\n

Add custom swipe actions to views in containers such as scroll views, stacks, grids, or custom layouts using swipeActions(edge:allowsFullSwipe:content:onPresentationChanged:)<\/code><\/a> and swipeActionsContainer()<\/code><\/a>.<\/p>\n

[…]<\/p>\n

Use the visibilityPriority(_:)<\/code><\/a> modifier to prioritize important toolbar actions so SwiftUI keeps them visible as space shrinks, moving lower-priority items to the overflow menu first.<\/p>\n

[…]<\/p>\n

Present an alert or confirmation dialog from an optional data item or error object, and use that data to produce the content and title[…]<\/p>\n<\/blockquote>\n\n

What’s new in SwiftUI<\/a>:<\/p>\n

\n

Explore the latest additions to SwiftUI and discover how they can improve your apps. We’ll introduce a new Document protocol with direct disk access and snapshot-based diffing for building high-performance apps; new APIs for reordering content in lists, grids, and sections; and toolbar enhancements including visibility priority and auto-minimizing behavior. We’ll also cover expanded presentation APIs — including swipe actions on any view — plus AsyncImage caching improvements and lazy state initialization for Observable types.<\/p>\n<\/blockquote>\n\n

Use SwiftUI with AppKit and UIKit<\/a>:<\/p>\n

\n

Discover how to incrementally adopt SwiftUI in your existing AppKit or UIKit app. We’ll show you how to use the Observation framework to automatically update your views, integrate SwiftUI components into an existing view hierarchy, and bring gesture recognizers into SwiftUI. We’ll also explore how to add complete SwiftUI scenes to your app without changing your overall architecture.<\/p>\n<\/blockquote>\n\n

Dive into lazy stacks and scrolling with SwiftUI<\/a>:<\/p>\n

\n

Discover the inner workings of lazy stacks in SwiftUI. We’ll explore how LazyVStack and LazyHStack estimate sizes, lazily load subviews, and prefetch content to deliver smooth scrolling experiences. We’ll also cover advanced performance optimizations, state management best practices, and tips for precise programmatic scrolling. To get the most out of this session, we recommend basic familiarity with SwiftUI layout using stacks.<\/p>\n<\/blockquote>\n\n

Compose advanced graphics effects with SwiftUI<\/a>:<\/p>\n

\n

Discover how to craft rich, custom experiences by creatively composing SwiftUI layout and graphics APIs. We’ll show you how to break down complex designs and use a creative pipeline to chain simple building blocks together. Learn how to draw with layer shaders, animate with timelines, and anchor views with alignment guides.<\/p>\n<\/blockquote>\n\n

Build powerful drag and drop in SwiftUI<\/a>:<\/p>\n

\n

Follow along as we build a game of Solitaire to explore the latest drag-and-drop capabilities in SwiftUI. We’ll show you how to use the new reordering API to let people arrange content, implement drag containers to move multiple items at once, and customize the drag-and-drop lifecycle to fit your app’s rules.<\/p>\n<\/blockquote>\n\n

There are also a bunch<\/a> of<\/a> labs<\/a>.<\/p>\n\n

Natalia Panferova<\/a>:<\/p>\n

\n

Up until now it was a property wrapper conforming to the DynamicProperty<\/code> protocol, but in Xcode 27 it becomes a Swift macro. In this post we will look at what the change means for @Observable<\/code> models stored in @State<\/code>.<\/p>\n<\/blockquote>\n\n

Malcolm Hall<\/a>:<\/p>\n

\n

Only took 3 years lol!<\/p>\n<\/blockquote>\n\n

Majid Jabrayilov<\/a>:<\/p>\n

\n

SwiftUI also introduces a new prominent<\/em> tab role. You can use the prominent<\/em> role for trailing-separated tabs, similar to search.<\/p>\n

[…]<\/p>\n

Document-based apps get a refreshed look and feel, along with a performance boost. It looks like Xcode has started using these improvements, which might explain why we see so much work around document-based apps this year. And finally, Xcode introduces SwiftUI Specialist and What’s New in SwiftUI skills for agentic coding in Xcode.<\/p>\n<\/blockquote>\n\n

Fatbobman<\/a>:<\/p>\n

\n

For me, the biggest change in SwiftUI comes from its comprehensive support for document-based apps. It not only adds a large number of new APIs, but also shifts the mental model toward “observable document objects + asynchronous snapshots + dedicated readers \/ writers.” This is clearly better suited to complex document apps, and it also aligns more closely with the overall evolution of modern Swift around Observation and Concurrency.<\/p>\n

The sessions also mentioned that SwiftUI continues to optimize layout- and container-related implementations, bringing noticeable performance improvements in some scenarios. This is an improvement developers have urgently needed. However, SwiftUI still does not provide the ability to create custom Lazy containers, which remains a clear disappointment.<\/p>\n<\/blockquote>\n\n

Natalia Panferova<\/a>:<\/p>\n

\n

iOS 27 introduces new reordering APIs that work with any container. We can mark dynamic content with reorderable()<\/code> and define the scope of the interaction with reorderContainer(for:)<\/code>. SwiftUI handles the drag preview, insertion placeholder, and drop animation, while our code applies the resulting change to the model.<\/p>\n

SwiftUI’s drag container APIs are also now available on iPhone and iPad, after previously being limited to macOS. They let us make items in a collection draggable without making the collection reorderable, and include multiple selected items in the same drag. The APIs also support lazy generation of transferable values and drag-session observation.<\/p>\n<\/blockquote>\n\n

robb<\/a>:<\/p>\n

\n

I love the new #SwiftUI Text selection but without a way to make selection span multiple Texts in a group, it doesn’t really address our needs at Linear – here’s hoping we see an update in a later seed 🤞<\/p>\n<\/blockquote>\n\n

Natalia Panferova<\/a>:<\/p>\n

\n

The NavigationTransition<\/a> protocol has been available in SwiftUI since iOS 18, letting us control how views animate when pushed onto a NavigationStack<\/code> and when presenting sheets and full-screen covers. We specify the transition using the navigationTransition(_:)<\/code> modifier on the destination or presented view, and SwiftUI uses it instead of the default animation for that context. Before iOS 27, SwiftUI provided two built-in conforming types: AutomaticNavigationTransition<\/code>, used via the automatic<\/code> static value, which defers to the system default for the current context, and ZoomNavigationTransition<\/code>, used via zoom(sourceID:in:)<\/code>, which animates the presented view expanding from a source view marked with matchedTransitionSource()<\/code>. iOS 27 introduces CrossFadeNavigationTransition<\/a>, a new built-in transition that cross-fades between views without requiring a source, and adds AnyNavigationTransition<\/a>, a type eraser that lets us select a transition at runtime.<\/p>\n<\/blockquote>\n\n

Kyle Howells<\/a>:<\/p>\n

\n

The last few years watching WWDC has been a mixed experience for me, because I honestly believe Swift and SwiftUI are actively either bad or being made worst.<\/p>\n

Yet every year, the problems I have with them are doubled down on, not improved.<\/p>\n<\/blockquote>\n\n

Kyle-Ye<\/a>:<\/p>\n

\n

The FB21333309 cache bug I submitted is now confirmed to be fixed on iOS 27.<\/p>\n

Instead of introducing a new CacheKey like I suggested, SwiftUI team choose to move the intensity payload out of the FeedbackType enum to a new Payload enum and add a new payload var to SensoryFeedback storage.<\/p>\n<\/blockquote>\n\n

dasdom<\/a>:<\/p>\n

\n

A few weeks ago I realised that most iOS jobs require knowledge of SwiftUI. So I started to rebuild my Mastodon client in SwiftUI. Then I got an offer for a new job and accepted it. \nThis means I can get back to working on the ObjC version. Feels good. :)<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n