Swift version: 5.6
You can – and should – read the thermal state of your device before doing any intensive work, because if the system is already under pressure you might find your app becomes unresponsive, even with basic things like animations.
You can read the current thermal state using ProcessInfo.processInfo.thermalState
, which has four values:
.nominal
you can proceed as normal and do all the work you want..fair
you should consider delaying any work that isn’t visible to users..serious
the system is working at high capacity and you should scale back the CPU, GPU, and I/O work you do..critical
the system is unable to keep up with all the work that is being done, so your user interface is likely to stutter – now is a bad time to do any sort of animation.The latter two of those are important to monitor, because users will notice – at .critical
level you can expect their device to be hot to the touch, so hopefully your app isn’t the cause of that!
TAKE YOUR SKILLS TO THE NEXT LEVEL If you like Hacking with Swift, you'll love Hacking with Swift+ – it's my premium service where you can learn advanced Swift and SwiftUI, functional programming, algorithms, and more. Plus it comes with stacks of benefits, including monthly live streams, downloadable projects, a 20% discount on all books, and free gifts!
Sponsor Hacking with Swift and reach the world's largest Swift community!
Available from iOS 8.0
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.