1 minute read

Using SF Symbols for clearer iOS interfaces

SF Symbols gives an iOS app a consistent, compact vocabulary for interface icons. The symbols scale cleanly, work with Dynamic Type, and feel native across Apple platforms that support them. Used with restraint, they reduce visual clutter without making important actions harder to find. They are especially useful for a small development team, where a shared icon language saves time and prevents each screen from developing its own visual dialect.

The quickest route is UIKit. Create an image with UIImage(systemName:), adjust it with UIImage.SymbolConfiguration, and place it in an UIImageView or button configuration. This avoids shipping separate assets for common pictograms and gives symbols the platform’s familiar weight and geometry. It also lets one catalogue support navigation bars, tab bars, alerts, and empty states without giving each component a different icon style.

A symbol is not automatically the right icon merely because it exists. Its name describes the drawing, not whether users will understand the intended action. A magnifying glass might imply search, while a location arrow can mean both position and direction. Before choosing one, write down the action in plain language, then compare several candidates under the app’s real size and contrast settings.

For teams serving Australia, that decision also involves a varied device base and practical daily settings. A commuter checking a bank app on the Melbourne Metro may view it outdoors and with one hand, while a regional user may have a smaller screen or an older iPhone. Native symbols are a strong starting point, but accessibility, localisation, and clear wording determine whether they work in the Australian market.

Establish a reliable symbol foundation

SF Symbols became available in iOS 13, so an app supporting earlier releases needs another strategy. In a modern app, set a realistic deployment target and check the symbol catalogue included with your current Xcode. The catalogue reveals names, variants, weights, and availability; a symbol added in a recent iOS release can return nil when running on an older operating system.

Keep names in one catalogue rather than scattering string literals across view controllers. A small wrapper can apply consistent sizing and weight while preserving the optional result that tells you when a symbol is unavailable:

extension UIImage {
    static func symbol(
        _ name: String,
        pointSize: CGFloat = 17,
        weight: UIImage.SymbolWeight = .regular
    ) -> UIImage? {
        let configuration = UIImage.SymbolConfiguration(
            pointSize: pointSize,
            weight: weight
        )
        return UIImage(systemName: name, withConfiguration: configuration)
    }
}

The catalogue should also define a fallback asset for essential actions. For example, an unfamiliar share symbol could fall back to an asset named Share, while a standard action such as search could use an older but widely supported symbol. Record the intended meaning beside each entry so future screens remain consistent and a renamed or newly deprecated symbol does not silently change the interface.

Create a clear visual hierarchy

Weight carries meaning in a symbol set. A bold, filled symbol naturally attracts more attention than a light outline, which makes mixed weights useful for navigation, toolbars, selected tabs, and destructive actions. Establish a small set of approved roles, such as regular for supporting information and semibold for selected or primary actions. Applying those roles consistently communicates importance without adding labels everywhere.

Rendering modes provide another layer of control. A monochrome template symbol can inherit the button’s tint, while hierarchical and palette configurations can distinguish parts of the same drawing. Use withTintColor(_:renderingMode:) when you need a single system colour, and use .alwaysOriginal when a palette must preserve multiple colours. Colour should reinforce hierarchy rather than become the only way to distinguish two states.

Choose symbols according to function, not visual similarity. A heart often communicates a favourite, but some apps use it for health records; a bookmark can mean saved content, reading position, or a literal marker. Check the surrounding copy, test with the target audience, and replace an ambiguous symbol with visible text. A compact interface still benefits from a short label whenever the destination or consequence of an action is not immediate.

Design for accessibility and changing conditions

Dynamic Type should change a symbol’s size alongside its surrounding text. For an UIImageView, set adjustsImageSizeForAccessibilityContentSizeCategory to true and begin with a base size that matches the associated text style. Avoid forcing every symbol to a fixed 24-point size, because that can make an interface look inconsistent when users enlarge text. The symbol itself should never crowd or obscure its label.

Every icon-only control also needs an accessible name. Assign a concise accessibilityLabel such as “Share document” or “Open filters”, and remove the image from the accessibility tree when a nearby text label already provides the same information. A VoiceOver user should hear the action, not a symbol identifier such as “square and arrow up”. Keep the tap target at least 44 by 44 points even when the visible drawing is much smaller.

Symbols must also remain understandable in increased-contrast mode, reduced transparency, bold text, and Reduce Motion. Test whether thin strokes disappear against a coloured background, and never rely on red and green alone to communicate status. Animation can provide useful feedback, but optional effects such as a pulse or bounce should stop or remain restrained when the user has requested reduced motion. A moving symbol should never be the sole explanation of a state change.

Localise meaning for Australian users

Australian English follows conventions such as “colour” and “favourite”, but a symbol name in Swift remains an implementation detail rather than translated interface copy. Put the meaningful wording in a localisable string and use the symbol as its visual support. This also protects symbols that are culturally ambiguous. For instance, a generic dollar-sign symbol does not identify Australian dollars, so pair it with A$ when the currency matters.

Right-to-left support requires another review. Apple provides mirrored or directional variants for some symbols, but not every drawing should be flipped mechanically. A backward chevron may need to mirror, while a forward arrow representing the next stage of a process may need to remain directional within the journey. Preview the app in Arabic or Hebrew if those languages are supported, and ensure button placement also follows the reading direction.

Everyday Australian app use makes this clarity practical. People check balances while commuting, compare supermarket baskets, and scan transport departures between cities such as Sydney, Melbourne, Brisbane, and Perth. Banking, retail, and transport apps compete in a crowded local market, so a recognisable symbol can save time only when it matches a familiar action. Keep it consistent with local terminology, show a text label for specialised actions, and confirm that it remains clear in both light and dark appearances.

Test, maintain, and close the feedback loop

Test the symbol catalogue across every supported iOS version, not only the newest simulator. Include the oldest realistic device size, VoiceOver, bold text, the largest Dynamic Type setting, Dark Mode, Increase Contrast, and every supported language. Preview a screen in Xcode, then verify the real behaviour on a device because rendering and touch areas can differ. Snapshot tests can also detect an accidental change in an icon’s availability or appearance.

Accessibility and privacy also need plain language. Australian Government services commonly benchmark against WCAG 2.1 AA, while the Disability Discrimination Act 1992 can apply to digital services. Under the Privacy Act 1988 and Australian Privacy Principles, where applicable, consent and privacy choices require meaningful disclosure; a shield or tick cannot replace an explanation of what data is collected or shared. If an external Vladogroup team is supporting the build, make symbol names, fallbacks, and accessibility results part of the acceptance criteria.

Keep the catalogue in version control, document each fallback, and review it after major iOS releases for newly available or deprecated symbols. The next concrete step is to add one labelled symbol to the current screen and verify it with VoiceOver at the largest Dynamic Type size.

Updated: