Sign in Subscribe

SwiftUI

A collection of 5 issues

Branching Haptics in SwiftUI: Getting More Out of sensoryFeedback

Most apps reach for sensoryFeedback exactly once and wire it to a single outcome: a button tap plays .impact, a save plays .success. That works, but it leaves most of the API on the table. The modifier was built to branch — one declaration can pick a different haptic for success,

Per-Glyph Text Animation in SwiftUI with TextRenderer

Text animation in iOS has always been awkward. To animate individual characters — a wave effect, a staggered entrance, per-letter color shifts — you either dropped into UIKit with NSTextStorage and CALayer gymnastics, or built a fragile HStack of individual Text views and lost kerning and line-wrapping in the process. iOS 18

ContainerValues: Per-Item Customization in SwiftUI Containers

If you've ever needed one child view in a SwiftUI container to look or behave differently from its siblings, you've probably reached for @Environment — and paid the price. Environment values propagate to every descendant in the subtree, not just the direct children of your container. Set

WebPage: iOS 26’s Headless, Observable Browser — No UIKit Required

Most apps that need to load a web page reach for WKWebView wrapped in a UIViewRepresentable — a layer of UIKit glue that was never pleasant to write and became less defensible with every SwiftUI release. iOS 26 ships a cleaner answer: WebPage, a fully @Observable model object that loads URLs,

Stress-Test Your SwiftUI Accessibility in a Single Preview

Most iOS developers test accessibility one setting at a time: flip Bold Text on, check the layout, flip it off, bump Dynamic Type up, check again. The problem is that your users don't toggle one setting in isolation — they set up their device once and forget about it.