{"id":52313,"date":"2026-06-18T14:56:01","date_gmt":"2026-06-18T18:56:01","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=52313"},"modified":"2026-06-18T14:58:19","modified_gmt":"2026-06-18T18:58:19","slug":"uikit-in-ios-27","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/06\/18\/uikit-in-ios-27\/","title":{"rendered":"UIKit in iOS 27"},"content":{"rendered":"

iOS & iPadOS 27 Beta Release Notes<\/a>:<\/p>\n

\n

[You] can use UIScene.extendStateRestoration<\/code> and UIScene.completeStateRestoration<\/code> to extend state restoration for UIScene.ActivationState.background<\/code> to UIScene.ActivationState.foreground<\/code> lifecycle transitions.<\/p>\n

[…]<\/p>\n

iOS and iPadOS apps built with the 27.0 SDK or later are required to include a launch screen.<\/p>\n

[…]<\/p>\n

Siri can load resources from drag interactions installed in your app’s interface.<\/p>\n

[…]<\/p>\n

In apps built with the iOS 27.0 SDK, a presented view controller inherits its trait collection by walking up its view’s superview chain through the intermediate views of the presentation, rather than jumping directly to the presentation controller.<\/p>\n<\/blockquote>\n\n

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

\n

Use UICollectionViewCompositionalLayoutSectionProvider<\/code><\/a> closures as part of automatic observation tracking to automatically invalidate and update compositional layouts when observable objects change.<\/p>\n

[…]<\/p>\n

Use UIRefreshControl<\/code><\/a> and UIStepper<\/code><\/a> in Mac apps built with Mac Catalyst. These controls are now fully supported in the Mac idiom.<\/p>\n

[…]<\/p>\n

Starting in iOS 27, apps built with the latest SDK must use the scene-based life cycle or they fail to launch.<\/p>\n

[…]<\/p>\n

Use NSTextTable<\/code><\/a>, NSTextBlock<\/code><\/a>, and NSTextTableBlock<\/code><\/a> to represent table structures in attributed strings.<\/p>\n<\/blockquote>\n\n

Modernize your UIKit app<\/a>:<\/p>\n

\n

Discover the latest updates to UIKit. Learn how to update your iPhone app layouts to work great when resized with iPhone Mirroring and on iPad. Explore new APIs for tab and navigation bars, find out how to prepare your app for new Apple Intelligence capabilities, and get introduced to a skill for your coding agent of choice that helps modernize your codebase.<\/p>\n<\/blockquote>\n\n

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

\n

iOS 27's UIKit is a tiny release in terms of API changes, but does have some changes. There are no new top-level paradigms, but there’s an new addition to TextKit 2<\/strong>, a new scene accessory<\/strong> API, Liquid-Glass-era bar minimization<\/strong> controls, and a small amount of quality-of-life additions to menus, tab bars, and drag interactions.<\/p>\n<\/blockquote>\n\n

Hartley Charlton<\/a>:<\/p>\n

\n

Apple appears to be laying the groundwork for a foldable iPhone in iOS 27, with new references discovered in the operating system’s frameworks and a notable emphasis on flexible app layouts at this year’s Platforms State of the Union.<\/p>\n<\/blockquote>\n\n

Jordan Morgan<\/a>:<\/p>\n

\n

The nav bar and its friends got quite a bit of attention, and to be honest that’s where we will find most of the changes. They adapt to all sorts of sizes and situations…hmmm, I WONDER WHY<\/a>!?<\/p>\n

[…]<\/p>\n

A few years ago, I wondered if UIKit would be deprecated altogether. That would’ve been drastic, sure, but I did<\/em> wonder. These days, I don’t share the same concern anymore. SwiftUI gets better each year, and yeah — it’ll have top billing. But UIKit is solid, and it appears to be a core part of Apple’s strategy into the future.<\/p>\n

Not much changed this year, and not much was added that’s flashy. But, that’s true of iOS 27 in several ways.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n