How to back port new SwiftUI APIs to older iOS versions

WWDC brings shiny new SwiftUI APIs. Your users are still on iOS 17 (or older). What now?

What this video covers:

Detecting API availability with #available and if #available
Creating custom backported modifiers that mimic new APIs
Using ViewBuilder to conditionally apply APIs
Wrapping UIKit components when SwiftUI APIs don't exist
Maintaining clean code without #available sprawl

Real examples:

Backporting scrollTransition to older iOS
Custom swipe actions before native existed
Navigation stack APIs before NavigationStack

Perfect for developers maintaining apps with wide iOS version support who still want to use modern patterns where possible.

In partnership with

Fastlane alternative – CLI tools

Are you tired of Ruby and Fastlane installation issues? There's got to be a better way! Discover Codemagic open source CLI tools. It is not a drop-in replacement for all of what Fastlane does (screenshots for example), but we use it at Codemagic to build and publish iOS and Android apps, also versioning and device provisioning.

View on GitHub

How to back port new SwiftUI APIs to older iOS versions

Navigation

Jobs by Level

Jobs by Work Type

Jobs by Employment Type

Jobs by Company Size

Top iOS Authors

Resources

Community