Here it is! What's New in UIKit in iOS 26.
This was a pretty mammoth undertaking, and it shows – a whopping 64 minute read!
I'll be keeping this article up to date over the beta cycle. Possibly littered with errors. Shout at me if I've made any stupid mistakes.
Link below 👇
Fun private property of UIMenu: _pinnedFooterElement.
This is how UIKit displays a persistent Siri AI menu element at the bottom of context menus. This API has been available internally since iOS 26.
Interestingly, _UIContextMenuListView (the view responsible for rendering the context menu content) uses a UICollectionView and modern diffable data source APIs.
The collection view is also using a compositional layout, allowing the pinning of the footer view to be handled by an NSCollectionLayoutBoundarySupplementaryItem with pinToVisibleBounds set to true.
The footer view itself is an instance of _UIContextMenuPinnedFooterView, a UICollectionViewCell subclass. The content is rendered by the shared _UIContextMenuCellContentView class.
Also, the backdrop blur behind the pinned element is achieved using _UIScrollPocketInteraction.
I had to _slightly_ change my approach, adjusting the top contentInset instead of layoutMargins for the header inset, but this was largely plug and play.
I also added fractional content offset logic so that when the bounds of the scroll view changes, the content offset adapts to ensure the scroll view is roughly scrolled to the same position.
A little late to the game, but I've started working on Duet's iPhone Duo layout. Namely, the Memory view.
Quite happy with how this experiment worked out, time to bring it into the project and iron out all the edge cases I've inevitably forgotten about...
This feels tone-deaf from Ternus. Apple’s software quality has taken a nose dive in recent years. SpringBoard is riddled with UI bugs and glitches on their $2000 foldable — a device which should set the standard for its product category.
The last thing the SWE org needs to do is “speed up”.
As a result of the above, it works just like any other UIScrollView, the API client can anchor content to the layoutMarginsGuide, frameLayoutGuide, or contentLayoutGuide, optionally vending a headerView and preferredHeaderAspectRatio which may or may not be respected based on the current layout environment.
This is a simple UIScrollView subclass, that overrides layoutSubviews to update the layoutMargins depending on a few factors:
1. The preferred header placement (resolved from the traitCollection's verticalBarEdge and horizontalSizeClass.
2. The vertical division reserved region's width and isActive status.
3. The trait collection's layoutDirection, either rightToLeft or anything else.
A little late to the game, but I've started working on Duet's iPhone Duo layout. Namely, the Memory view.
Quite happy with how this experiment worked out, time to bring it into the project and iron out all the edge cases I've inevitably forgotten about...
The good folks working on UIKit finally fixed the jiggly UIMenu dismissal bug in 27.2 😭
I think this got fixed for the zoom transition in 27.1? Glad to see the fix make its way to menus too!
PSA for @one_sec_app users:
iOS 27.2 is out and it contains TONS of Shortcuts / Automations bug fixes, speed & reliability improvements.
Highly recommend to update soon!
Big shout-out to the Shortcuts team for all your amazing work this summer 🫶