Swift version: 5.1
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 Instabug helps you identify and resolve severe crashes quickly. You can retrace in-app events and know exactly which line of code caused the crash along with environment details, network logs, repro steps, and the session profiler. Ask more questions or keep users up-to-date with in-app replies straight from your dashboard. Instabug takes data privacy seriously, so no one sees your data but you! See more detailed features comparison and try Instabug's crash reporting SDK for free.
The biggest ever Hacking with Swift sale is now on, letting you save 50% on all books and bundles. Learn something new with Swift and enjoy great savings while the sale lasts!
Available from iOS 13.0
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.