ビスター(Vistar)

@morrisinlife You can get a ZoomTransition with a popover, but as far as I know, confirmationDialog only supports ZoomTransition when presented from a UIBarButtonItem.

@Lmssync Not quite the same. Maybe I'm doing it wrong?

Question for the internet: Does anyone know how to do this in SwiftUI?

@morrisinlife So you mean creating a smooth transition where a View shrinks into a small popover-like View but not using a toolbar?

@Lmssync Turns out it works perfectly in the toolbar, but not in the body

@ertembiyik I personally think it’s better to use the properties with the equivalent propertie on UITraitCollection rather than UIScreen since UIScreen.main is deprecated.

@_Kavsoft nice finding! there is a simpler api that works pretty much on any os version: UIScreen.main.value(forKey: “_displayCornerRadius”) as? CGFloat

I recently discovered that the SwiftUI EnvironmentValues infant contains Device Corner Radius value, but it’s not available for use. However, we can easily extract those values using a simple String Regex. With this information, we can basically Backport the ConcentricRectangle shape for older iOS versions as well. For More, check out this video. youtu.be/D6vOHiBpemM NOTE: I tested this even with iOS 16, and the value is indeed present. It’s possible that it’s available for even older versions, but I haven’t tested it yet.

@flyosity I personally agree with this take the most on when to use SwiftUI vs. UIKit! 🙌

If you care about UI performance at the deepest level of your soul, you need to use UIKit for scrolling lists and timelines Use SwiftUI for onboarding, settings, modals, etc. x.com/jacobtechtaver…

@jeudesprits Thanks! If CAMatchMoveAnimation and CAMatchPropertyAnimation aren’t available, would you recommend using UIUpdateLink (haven’t tried it yet 🤔) or CADisplayLink to achieve similar real-time synchronization?

CAMatchMoveAnimation and CAMatchPropertyAnimation have begun to be actively used in liquid glass. In many cases, you simply want to mirror certain properties of the sourceLayer in real-time. Apple uses MatchMove for the position key and multiple MatchProperty instances for the hidden, cornerRadius, and meshTransform keys, added with duration=infinity to replicate the shape of the layer to which the effect is applied.

Gonna try this with CADisplayLink... if it doesn’t work, I might switch to CAMatchMoveAnimation 😅 Has anyone here already ventured into the world of CAMatchMoveAnimation?

@SebJVidal At this point it’d probably be quicker to implement my own UIFlexInteraction 😂

Trying to whip up a nice animation for this play control. At some point the UIKit team fixed UIGlassEffect's ability to animate in/out which was broken in 26.0 but it's still not perfect... Notice the transform applied by _UIFlexInteraction resetting without animating. 🥹

@Barbapapapps It seems to be an animation where the render server resolves transforms from a source layer’s points in a different coordinate space and transfers them onto a target layer. Used for effects like a view “jumping” from a sheet to a specific spot 🚀

@Lmssync Never heard of it! Is this a matchedGeometry like effect at the CoreAnimation layer?

@cifilter It presumably resolves displacement, rotation, and scale from source layer’s point set across coordinate spaces atomically within the render server, transferring them to the target layer without touching the main thread.

@Lmssync How does it work? Does it diff the incoming layer tree looking for a layer with the same id/namespace to map the animation?

@SebJVidal This approach is needed for “filters.gaussianBlur.inputRadius”, but it looks like some filter properties are already recognized as animatable 🤔

Reasonably nice API, you can set any UIView's additionalAnimatableProperties...property to a Set of Strings. Something like ["filters.gaussianBlur.inputRadius"]. Used a Set instead of an Array for O(1) contains(_:) lookup.

Some Objective-C Runtime trickery to enable UIKit-based animations on properties that, by default, aren't animatable. Wrote this to enable CAFilter animations without requiring a UIView subclass overriding _shouldAnimatePropertyWithKey:

Here’s the doc for the deprecated API: developer.apple.com/documentation/… For the record, the replacement for this API is accessibilityShowBorders. It was introduced recently, but it’s back-deployed, so you can use it safely on older OS versions. developer.apple.com/documentation/…

Apple docs say this API is supported until iOS 1000.0. Nice to know SwiftUI will outlive humanity 😂

@Barbapapapps Whoa 😭

@Lmssync pocketForEdge was also removed 😭

Does anyone know why I don’t get the blur effect and such a light black overlay on this view (scroll edge effect), whereas in Settings it works as intended? The setup is pretty much the same (UINavigationController) ☹️

@Barbapapapps -[UIScrollView _pocketForEdge:makeIfNeeded:] (still not removed?) or somewhere inside UIScrollView’s subviews.

@Lmssync How do you even get that _UIScrollPocket? UIScrollView used to have _UIScrollPocket *_topPocket (iOS 26.0), but it’s gone now (iOS 26.3)😵‍💫 I tried accessing it through UIScrollView._edgeEffectViewInteraction -> topPocket, but no luck.

@SwiftDev_UI 🙋

is anyone noticing a major lag/whitescreen when running the 26.4 simulators from Xcode 26.4? still present in the latest beta. it waits about 30 seconds on the white screen before the app actually launches, on 26.2 simulator with Xcode 26.3 no issues at all.

@Barbapapapps Does -[UIScrollPocket setReducedTransparency:true] improve it a bit? Overriding props is becoming a pain now that they’re defining these symbols in Swift🙃

@Lmssync 😭

_UIFlexInteraction might have gotten a check for this accessibility added 🤔

@jrsaruo_tech watchとmacにならありますが、iOSにはないですね 単なるpadding()は固定値のはずです developer.apple.com/documentation/…

SwiftUIでlayoutMarginsGuide的なものってあったっけ？システム標準の余白って端末によって16ptになったり20ptになったりしたと思うけど単にpadding()だけでいけるんだっけ…？