Supporting Objective-C in a Swift codebase

on YouTube ↗04m

" summary

GitHub shows roughly 100k vs 70k pull requests and Stack Overflow reports ~6.5% usage for both Swift and Objective C, so interoperability matters. Presents concrete workarounds: expose an NSNumber-backed @objc property as an Objective‑C fallback for an Int? optional, add Objective‑C unit tests to catch unbridgeable APIs, and enforce a custom linter rule that warns when protocols, enums, generics or structs are not bridgeable. Each item is actionable and verifiable in the codebase.

AI-written summary · about

" chapters (6)

1. 0:00Introduction
2. 0:26Why you should care
3. 0:40ObjectiveC vs Swift
4. 1:36ObjectiveC fallback
5. 2:36ObjectiveC unit tests
6. 3:07linter rule

" related talks

• 40mFeet in Both Worlds: From Objective-C to SwiftAndy Matuschak · Strange Loop 2015
• 19mUsing C, C++ and Objective C frameworks in Swift appsCecilia Humlelu · try! Swift Tokyo 2019
• 19mJust Enough Objective-CDaniel Jalkut · dotSwift 2019
• 37mBeyond XcodeEric Bariaux · SwiftLeeds 2025
• 49mEffective Kotlin-Swift InteroperabilityJohn Rodriguez · KotlinConf 2019
• 41mThe Kotlin Swift boundaryRussell Wolf · Chicago Roboto 2021
• 25mUse C, C++ and Objective C Libraries in a Swift ProjectCecilia Humlelu · App Builders Switzerland 2019
• 58mSwift: safety, ergonomics, productivity and legacy preservationFellipe Caetano · QCon São Paulo 2018