Apple engineers explain how to maximize app responsiveness in SwiftUI, monitor foundation model performance, and reduce battery usage.
Join us online to learn how to elevate your app experience by maximizing performance and resolving inefficiencies. Whether you’re optimizing an existing app or just starting out, you’ll learn how to improve your app's responsiveness with SwiftUI, monitor performance when using foundation models, and explore ways to reduce your app's battery usage.
Introduction
Optimize power with the new design
Generate fast responses with Foundation Models
Dive deep into SwiftUI performance
Performance tools at Snap
Closing remarks
To explore additional sessions, appointments, and workshops, view the full schedule of Meet with Apple activities worldwide.
apple.co/Meet-with-Apple
More Apple Developer resources:
Video sessions: apple.co/VideoSessions
Documentation: apple.co/DeveloperDocs
Forums: apple.co/DeveloperForums
App: apple.co/DeveloperApp
Why it's here
2 people recommend this
What people say. Engineers highlight this session for its insights on SwiftUI performance pitfalls, such as closure-induced view re-evaluations.
k
u/kistasnikin r/swift • Recommends
On “Liquid Glass UI native or custom?”
It depends on how is used.
It would help if you could share with us a video demonstrating what looks wrong.
In latest Apple video I saw that liquid glass as beautiful as it looks it requires developer's attention (for performance and fps dropping reasons)
[video
On “SwiftUI View Actions: Parent-Defined Closures vs Observable Object Methods?”
link to this video at 1:37:05 shows you exactly why calling a function on a view model is better than passing a closure to the view.
Spoilers: closures are worse for performance. The closure (in your case) automatically captures an instance of the parent view, which means the child view is needlessly reevaluated whenever the parent view changes.