Swift version: 5.2
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:
.nominalyou can proceed as normal and do all the work you want.
.fairyou should consider delaying any work that isn’t visible to users.
.seriousthe system is working at high capacity and you should scale back the CPU, GPU, and I/O work you do.
.criticalthe 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!
SPONSORED Announcing NSSpain 2020: Remote Edition! An online, continuous conference for iOS developers. We’ll start on Thursday and finish on Friday, with talks, activities, and lots of fun for 36 hours, non-stop. Sound good? Join us!
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.