Swift version: 5.2
When specifying colors for objects in your views, it’s often easier to use the built-in semantic colors of
UIColor rather than specifying our own custom colors that might not look good in both light and dark mode.
For example, when you are coloring a label, use
.secondaryLabel, or similar so that UIKit will automatically make sure it stands out.
For backgrounds you should use
.secondarySystemBackground, or similar so that when you layer one view over another they don’t appear to become merged.
And when you’re using fixed colors like
.blue you should instead use
.systemBlue to get a color that will adapt to the user’s trait environment – it will be a lighter red when in dark mode, and a darker red in light mode, rather than the fixed pure red of
SPONSORED Would you describe yourself as knowledgeable, but struggling when you have to come up with your own code? Fernando Olivares has a new book containing iOS rules you can immediately apply to your coding habits to see dramatic improvements, while also teaching applied programming fundamentals seen in refactored code from published apps.
Available from iOS 13.0
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.
Link copied to your pasteboard.