# Objective-C Objective-C is a C programming language with object-oriented capabilities and a dynamic runtime. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Future of KMP's iOS Interop - Daniel Bertoldi DevFeed: [The Future of KMP's iOS Interop - Daniel Bertoldi]() Original publisher: [Read original article]() Published: 2026-06-12T00:00:00Z Content type: comparison Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Swift](), [Objective-C](), [Compiler](), [multiplatform]() Tags: [compare](), [experimental](), [interop](), [ios](), [kmp](), [kotlin](), [kotlin-multiplatform](), [native](), [objective-c](), [production](), [skie](), [swift](), [swift-export]() ### AI overview This comparison examines Kotlin Multiplatform iOS interoperability through Kotlin's experimental Swift Export and the Objective-C bridge enhanced by SKIE. It compares their generated output, capabilities, limitations, and tradeoffs. ### Source excerpt Kotlin's new Swift Export feature promises to eliminate the Objective-C middleman and generate native Swift APIs directly from your KMP code. But with SKIE already solving many of the same pain points in production today, which approach should your team bet on? We break down the capabilities, limitations, and tradeoffs of both. ## Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps DevFeed: [Using Dart FFI and C for Objective-C and Swift Interoperability in Flutter iOS Apps]() Original publisher: [Read original article]() Author: Marvin März Published: 2023-12-11T15:43:49Z Content type: tutorial Language: en Sources: [QuickBird Studios Blog]() Topics: [Dart](), [Flutter](), [interoperability](), [iOS](), [Swift](), [Objective-C](), [C](), [Code]() Tags: [c](), [dart](), [flutter](), [interop](), [interoperability](), [ios](), [objective-c](), [platform](), [post](), [swift]() ### AI overview This guide explains how Dart 2.18's Objective-C/Swift Interop lets Flutter applications call native iOS code from Dart through Dart FFI and C. It discusses limitations of platform channels, including duplicated boilerplate and maintenance concerns, and introduces the interop approach. ### Source excerpt Dart 2.18 introduced Objective-C/Swift Interop. In this comprehensive guide, we explore how to seamlessly integrate native iOS code into your Flutter app using Dart FFI and C as an interoperability layer. The post Platform Channels are Dead! Objective-C/Swift Interop is Here! appeared first on QuickBird Studios. ## Using annotations to improve iOS APIs on Kotlin Multiplatform DevFeed: [Using annotations to improve iOS APIs on Kotlin Multiplatform]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2023-09-19T00:00:00Z Content type: article Language: en Sources: [Posts on Marco Gomiero]() Topics: [Kotlin Multiplatform](), [interoperability](), [iOS](), [Objective-C](), [Swift](), [Kotlin](), [multiplatform]() Tags: [architecture](), [coroutine](), [interoperability](), [ios](), [kotlin](), [kotlin-multiplatform](), [mvvm](), [objective-c](), [swift]() ### AI overview This article explains how Kotlin 1.8 annotations can improve iOS APIs in a Kotlin Multiplatform project. It describes using @HiddenFromObjC and @ObjCName to expose iOS-specific implementations with clearer names while keeping shared business logic and reducing misleading duplicate class names. ### Source excerpt Kotlin 1.8 has introduced new annotations to improve the interoperability of Kotlin with Objective-C and Swift: @ObjCName: allows to customize the name that will be used in Swift or Objective-C @HiddenFromObjC: allows hiding a Kotlin declaration from Objective-C (and Swift). @ShouldRefineInSwift: it marks a Kotlin declaration as swift_private in the Objective-C API, allowing to replace it with a wrapper written in Swift. You can see the release announcement for more details about the interoperability improvements introduced with Kotlin 1.8. ## When iOS Engineers Should Use Kotlin Multiplatform's expect/actual Syntax DevFeed: [When iOS Engineers Should Use Kotlin Multiplatform's expect/actual Syntax]() Original publisher: [Read original article]() Author: Derek Lee Published: 2022-09-22T00:00:00Z Content type: opinion Language: en Sources: [art and science of coding]() Topics: [kotlin multiplatform mobile](), [Kotlin Multiplatform](), [Mobile](), [Kotlin](), [Objective-C]() Tags: [guide](), [kmm](), [kotlin](), [kotlin-multiplatform](), [mobile](), [objective-c](), [science]() ### AI overview This article argues that iOS engineers building multiplatform apps with Kotlin Multiplatform Mobile should generally write platform-dependent code in Swift instead of using the expect/actual syntax. It identifies building a multiplatform framework as the main case where the syntax may be worth considering and recommends consulting Apple's Objective-C documentation and Kotlin/Native headers when using it. ### Source excerpt TL;DR If you're an iOS engineer who wants to build multiplatform apps using KMM, the few benefits of using the expect/actual syntax do not outweigh those of writing your platform-dependent code in Swift. The use-case for iOS engineers to consider leveraging expect/actual syntax would be when building a multiplatform framework. If you're going to use expect/actual, be sure to reference Apple's Objective-C documentation over Swift documentation and use the Kotlin/Native headers for the most accurate representation of the iOS APIs available in Kotlin. The expect/actual Syntax of Kotlin Multiplatform Mobile (KMM) The Kotlin Multiplatform SDK includes a syntactical construct integrated into JetBrains IDEs that engineers can use to define classes and functions that are expect -ed (pun intended) to have platform-specific implementations. The actual implementations are also written in Kotlin separately for Android and iOS. When looking at the code modules in a KMM project: within the KMM shared framework module, you first define a class or a function as expected. Then the actual implementations are written for each supported platform module. The following example illustrates what module the code is defined within for Android and iOS: The `common` module defines the expected classes and functions, and platform modules define the actual implementation. We looked at some simple examples in the last blog. These examples are helpful because they allow us to wrap our heads around the concept before diving into something more complicated. I want to take you on a journey of writing some code using this approach to illustrate how this can become more complicated in practice than expected. In fact, I'm going to make a bold statement and propose that there's only a single scenario where you, the iOS Engineer, should even consider using the expect/actual syntax. This post is part of a series on Kotlin Multiplatform: The iOS Engineer's Guide to Beginning Kotlin Multiplatform Development ## Auto linking with Mach-O binaries DevFeed: [Auto linking with Mach-O binaries]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2022-02-24T02:00:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Objective-C](), [Swift](), [toolchain]() Tags: [assembly](), [clang](), [objective-c](), [swift]() ### AI overview This article explains automatic linking for Mach-O binaries. It shows how Objective-C compilation can embed linker options for dependencies such as Foundation, how to inspect those options, and how omitting module support causes explicit linking to be required. It also covers module maps, Swift standard-library dependencies, and several ways to add linker options manually with clang, swiftc, or assembly directives. ### Source excerpt Auto linking is a feature that embeds information in your binaries' at compile time which is then used at link time to automatically link your dependencies. This allows you to reduce the duplication of flags between the different phases of your (or your consumers') builds. For example, with this Objective-C file: #include int main() { NSLog(@"Hello, World!"); return 1; } Compiled with: $ clang -fmodules -c foo.m -o foo.o You can then inspect the options added for use at link time: $ otool -l foo.o | grep LC_LINKER_OPTION -A3 cmd LC_LINKER_OPTION cmdsize 40 count 2 string #1 -framework string #2 Foundation ... Now when linking this binary you don't have to pass any extra flags to the linker to make sure you link Foundation: $ ld foo.o -syslibroot `xcrun --show-sdk-path` To compare, if you compile the binary without -fmodules1: $ clang -c foo.m -o foo.o You don't get any LC_LINKER_OPTIONs. Then when linking the binary with the same command as before, it fails with these errors: $ ld foo.o -syslibroot `xcrun --show-sdk-path` Undefined symbols for architecture arm64: "_NSLog", referenced from: _main in foo.o "___CFConstantStringClassReference", referenced from: CFString in foo.o ld: symbol(s) not found for architecture arm64 To make it succeed you must explicitly link Foundation through an argument to your linker invocation: $ ld foo.o -syslibroot `xcrun --show-sdk-path` -framework Foundation Auto linking is also applied when using module maps that use the link directive. For example with this module map file: // module.modulemap module foo { link "foo" link framework "Foundation" } That you include with in this source file: @import foo; int main() { return 1; } And compile (with an include path to the module.modulemap file): $ clang -fmodules -c foo.m -o foo.o -I. The produced object depends on foo and Foundation. This can be useful for handwriting module map files for prebuilt libraries, and for quite a few other cases. You can read about thi ## \[Перевод\] От песочных часов к пирамиде: как усовершенствовать структуру тестов DevFeed: [\[Перевод\] От песочных часов к пирамиде: как усовершенствовать структуру тестов]() Original publisher: [Read original article]() Author: laechoppe (Badoo) Published: 2022-02-17T12:15:34Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [iOS](), [Objective-C](), [Swift](), [ui]() Tags: [badoo](), [ios](), [objective-c](), [qa](), [qa-automation](), [swift](), [tag-23c525fe15c9](), [tag-910b48292e17](), [tag-97ed25004d35](), [tag-e932065bc8da](), [testing](), [ui](), [xcuitest]() ### AI overview A tutorial on test automation for native iOS applications written in Objective-C and Swift. It explains the test pyramid, recommends many small unit tests, fewer medium-level tests, and very few high-level end-to-end or UI tests, and discusses how projects can develop an unbalanced testing structure. ### Source excerpt Меня зовут Владислав Романенко, я Senior iOS QA Engineer в Badoo и Bumble. Мы регулярно внедряем новые фичи в приложения, и автоматизация тестирования -- один из способов не пропустить баги. Фактически автотесты входят в жизненный цикл всех частей наших приложений: бэкенда, сервисов, фронтенда и мобильных клиентов. Чем раньше мы обнаружим ошибку, тем дешевле будет её исправить. Сегодня я расскажу об автоматизации тестирования в iOS, потому что на протяжении всей своей карьеры в Badoo я плотно занимался тестированием наших нативных iOS-приложений, которые написаны на Objective-C и Swift. Хотя кое-где я буду упоминать характерные для iOS инструменты и термины (например, XCTest), общие принципы и подходы универсальны. Так что, даже если в вашем проекте используется совсем другой стек, статья будет вам полезна. Читать далее ## Getting Square's iOS build ready for Apple Silicon with Bazel DevFeed: [Getting Square's iOS build ready for Apple Silicon with Bazel]() Original publisher: [Read original article]() Author: Jerry Marino Published: 2022-01-27T20:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [bazel](), [iOS](), [build times](), [cpu](), [Objective-C](), [Swift](), [Open Source]() Tags: [apple](), [arm](), [bazel](), [build](), [build-times](), [caching](), [engineering](), [ios](), [objective-c](), [open-source](), [simulator](), [swift](), [x86]() ### AI overview Square describes adapting its Bazel-based iOS build system for Apple Silicon by building and running iOS applications on the M1 simulator. The article explains the available development paths and why device builds and x86_64 builds under Rosetta 2 were not selected. ### Source excerpt Building and running iOS builds using the M1 simulator ## An Approach for Migrating From Objective-C to Swift DevFeed: [An Approach for Migrating From Objective-C to Swift]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2022-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Steve Barnegren]() Topics: [Objective-C](), [Swift](), [interoperability](), [iOS](), [tvOS](), [generics](), [Code]() Tags: [apple](), [enums](), [generics](), [interoperability](), [ios](), [objective-c](), [optional](), [swift](), [types](), [with]() ### AI overview This article shares lessons from transitioning a large iOS and tvOS application from Objective-C to Swift. It explains why simply adding new Swift code produced limited progress and caused Swift code to be constrained by Objective-C interoperability. ### Source excerpt It feels like Swift is pretty ubiquitous across the Apple ecosystem now, but there's a lot of Objective-C out there. The larger and older the app, the more likely that there's still a bunch of Objective-C powering various bits behind the scenes. ## Kotlin Native -- Using swift, not Objective-C DevFeed: [Kotlin Native -- Using swift, not Objective-C]() Original publisher: [Read original article]() Author: Paul Woitaschek Published: 2021-11-19T08:00:42Z Content type: tutorial Language: en Sources: [YAZIO Engineering - Medium]() Topics: [kotlin-native](), [Code generation](), [Swift](), [Objective-C](), [Compiler]() Tags: [android](), [code-generation](), [compiler](), [interop](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [ksp](), [library](), [objective-c](), [swift]() ### AI overview This tutorial explains how YAZIO uses Kotlin Native for shared business logic while providing a Swift-native iOS API. It describes the limitations of Kotlin-to-Objective-C interoperability and shows how KSP and SwiftPoet can generate Swift mappings for Kotlin types such as enums and sealed classes. ### Source excerpt Kotlin Native -- Using Swift, not Objective-C At YAZIO we use Kotlin Native Extensively. The business logic of all new app features is exclusively written in Kotlin. In its core, every screen has one ViewModel which exposes a single Flow that the Android App and the iOS can consume to render the state. On Android, rendering the view state is no burden because it's the language we use in the Android App anyways. However this is different for iOS. While Swift does interop with Objective-C, the public API as seen from Swift is bad. A simple data class is exported as a regular class. The properties are not native Swift types. What should be a Bool becomes a KotlinBoolean. What should be come a Double becomes a KotlinDouble. But what we want is most of the times a struct with Swift types. These are the lesser evils, the greater ones are enums and sealed classes. In Objective-C, they both become regular classes. And therefore lose all the advantages they have when used from Swift. But what we want is a Swift enum. To overcome these restrictions for quite some time our iOS team has created mappings. There is a whole target, dedicated to mapping the Objective-C classes to Swift. Basically when developing a new feature, the whole public API is manually mapped to Swift. This is good because the result is a clean Swift-native API. But that's bad because it's extreme boilerplate and a real productivity killer. What if we could directly generate these mappings and use code generation to handle that for us? Turns out: There are two tools available that make it possible. The first one is KSP. It is basically a library that lets you implement a Kotlin compiler plugin and it gives you hooks to analyze the Kotlin Syntax Tree and generate code based on it. The second one is SwiftPoet. SwiftPoet is a library you can use to generate Swift code from Kotlin, similar to what KotlinPoet and JavaPoet do. Okay, let's get our handy dirty. For the basic setup, just follow the tutorial ## Kotlin Native -- Using swift, not Objective-C DevFeed: [Kotlin Native -- Using swift, not Objective-C]() Original publisher: [Read original article]() Author: Paul Woitaschek Published: 2021-11-19T07:21:13Z Content type: tutorial Language: en Sources: [Stories by Paul Woitaschek on Medium]() Topics: [kotlin-native](), [Kotlin](), [Swift](), [Code generation](), [Objective-C](), [Compiler](), [Library](), [Tutorial]() Tags: [android](), [code-generation](), [compiler](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [ksp](), [library](), [objective-c](), [swift](), [tutorial]() ### AI overview This developer article explains how YAZIO uses Kotlin Native for shared business logic while addressing the limitations of exposing Kotlin types through Objective-C to Swift. It describes manually mapping the generated API to Swift and introduces KSP and SwiftPoet as tools for generating Swift mappings and reducing boilerplate. ### Source excerpt Kotlin Native -- Using Swift, not Objective-C At YAZIO we use Kotlin Native Extensively. The business logic of all new app features is exclusively written in Kotlin. In its core, every screen has one ViewModel which exposes a single Flow that the Android App and the iOS can consume to render the state. On Android, rendering the view state is no burden because it's the language we use in the Android App anyways. However this is different for iOS. While Swift does interop with Objective-C, the public API as seen from Swift is bad. A simple data class is exported as a regular class. The properties are not native Swift types. What should be a Bool becomes a KotlinBoolean. What should be come a Double becomes a KotlinDouble. But what we want is most of the times a struct with Swift types. These are the lesser evils, the greater ones are enums and sealed classes. In Objective-C, they both become regular classes. And therefore lose all the advantages they have when used from Swift. But what we want is a Swift enum. To overcome these restrictions for quite some time our iOS team has created mappings. There is a whole target, dedicated to mapping the Objective-C classes to Swift. Basically when developing a new feature, the whole public API is manually mapped to Swift. This is good because the result is a clean Swift-native API. But that's bad because it's extreme boilerplate and a real productivity killer. What if we could directly generate these mappings and use code generation to handle that for us? Turns out: There are two tools available that make it possible. The first one is KSP. It is basically a library that lets you implement a Kotlin compiler plugin and it gives you hooks to analyze the Kotlin Syntax Tree and generate code based on it. The second one is SwiftPoet. SwiftPoet is a library you can use to generate Swift code from Kotlin, similar to what KotlinPoet and JavaPoet do. Okay, let's get our handy dirty. For the basic setup, just follow the tutorial ## KMM Oddity #1: Interface methods with underscores DevFeed: [KMM Oddity #1: Interface methods with underscores]() Original publisher: [Read original article]() Author: Yev Kanivets Published: 2021-09-20T04:23:21Z Content type: tutorial Language: en Sources: [xorum.io - Medium]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Objective-C](), [interfaces](), [Mobile](), [iOS](), [kotlin-native]() Tags: [android](), [compiler](), [interfaces](), [ios](), [kmm](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [mobile](), [multiplatform](), [objective-c]() ### AI overview This article examines a Kotlin Multiplatform Mobile interoperability oddity in iOS. It explains how the Kotlin/Native compiler can expose an interface method with an underscore suffix, such as eat(food_:), when similarly named methods from different interfaces may clash in Objective-C. ### Source excerpt Kotlin Multiplatform attracts more and more developers every day. Especially after the technology transitioned to the Alpha stage. On its way to Beta, KMP removes all major hassles (Memory Model, for example). Nonetheless, you can still find "a few" more minor bugs and oddities reported in Kotlin's YouTrack. They aren't blockers for using KMP in your production application but may cost you several hours of wondering what and why is happening in your mobile application (mainly on iOS). I faced many such issues myself since I've started using Kotlin Multiplatform Mobile two years ago. In this series of articles, I'll share my favorite oddities of KMM with explanations and workarounds (if possible). Kotlin/Native Obj-C interop Shared KMM modules are written in Kotlin, hence can be used in Android native applications as it is. On iOS, it's more complicated because of Objective-C and Swift, which can't directly use Kotlin code. Kotlin/Native plugin compiles shared KMM modules to iOS frameworks, which contain binary and Obj-C header. You can find them in the build folder of the shared module, under bin/iOS/. Many concepts of Kotlin don't exist in Obj-C, so specific shortcuts and workarounds need to be applied to make it work. It is where some oddities start appearing. Interface methods naming clash Let's say we have two types of pets -- Dog and Cat, which we need to feed with some specific Food. In Kotlin, we could represent that with two interfaces, each having an internal (embedded) Food class. https://medium.com/media/b868e0383cdc20566aef171daa863a87/href It works perfectly well in Android, but on iOS Dog will have eat(food_:) method instead of eat(food:). Where does that underscore suffix come from? And why do we need it? It looks like Kotlin/Native compiler thinks there will be a clash between eat(food:) methods of Dog and Cat interfaces, so it's safer to make them different by implicitly adding an underscore to the 2nd one. I'm not sure it will become a problem and i ## AppCode 2021.2: улучшения поддержки Swift, автодополнение выражений, окно иерархии вызовов для Swift и не только DevFeed: [AppCode 2021.2: улучшения поддержки Swift, автодополнение выражений, окно иерархии вызовов для Swift и не только]() Original publisher: [Read original article]() Author: yeswolf (JetBrains) Published: 2021-08-16T09:53:35Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [Swift](), [ide](), [Kotlin Multiplatform](), [swift-package-manager](), [async/await](), [Kotlin](), [multiplatform](), [Objective-C]() Tags: [appcode](), [async](), [await](), [call-hierarchy](), [complete-statement](), [ide](), [kmm](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [local-history](), [mobile](), [multiplatform](), [objective-c](), [swift](), [swift-package-manager]() ### AI overview This release article describes AppCode 2021.2 improvements, including support for Swift features such as result builders, enum Codable synthesis, and async/await. It also covers documentation completion, Call Hierarchy, Swift Package Manager build and debugging support, a Kotlin Multiplatform Mobile plugin, a debugger Preview Tab, and Local History search. ### Source excerpt Привет, Хабр! В этом посте, как и всегда, расскажем о новом релизе AppCode. Всем, кому интересно, -- добро пожаловать под кат. Читать далее ## Breaking Loose from Third-Party Lock-In with Custom Refactoring Tools DevFeed: [Breaking Loose from Third-Party Lock-In with Custom Refactoring Tools]() Original publisher: [Read original article]() Published: 2020-08-11T00:00:00Z Content type: tutorial Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Refactoring](), [Test-driven development](), [iOS](), [Swift](), [Objective-C](), [Xcode](), [Code](), [Software]() Tags: [ast-matchers](), [code](), [developers](), [ios](), [libtooling](), [llvm](), [refactoring](), [software](), [swift](), [technology](), [third-party](), [tools](), [xcode]() ### AI overview This article describes how SoundCloud automated the migration of more than 900 Objective-C Specta specification files to plain XCTest tests using custom refactoring tools. The effort removed Specta from the codebase while supporting ongoing iOS development in Swift. ### Source excerpt Code refactoring is an essential part of the job of software developers. As time goes on, technology evolves, product requirements change... ## Shipping Binary Frameworks With Swift 5.0 DevFeed: [Shipping Binary Frameworks With Swift 5.0]() Original publisher: [Read original article]() Author: Chris Williams Published: 2019-05-31T09:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Swift](), [Framework](), [Objective-C](), [Xcode]() Tags: [binaries](), [bridge](), [bridging](), [compatibility](), [engineering](), [how-to](), [objective-c](), [swift](), [toolchains](), [xcode]() ### AI overview This tutorial explains how to ship binary frameworks with Swift 5.0. It covers ABI stability, the future role of module stability, and using Objective-C bridging to provide a more stable interface across Swift toolchain versions. ### Source excerpt How to get a binary framework shipped with Swift 5.0 ## Developing on iOS and Android DevFeed: [Developing on iOS and Android]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2019-04-22T19:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Android](), [iOS](), [Mobile](), [multiplatform](), [Kotlin](), [Swift](), [Objective-C]() Tags: [android](), [development](), [engineering](), [ios](), [kotlin](), [mobile](), [multiplatform](), [objective-c](), [swift]() ### AI overview This article describes the convergence of iOS and Android development and the redundancy of maintaining separate implementations. It presents cross-team code reviews and an incremental multiplatform Kotlin experiment, beginning with replacing Objective-C persistence code using Kotlin/Native and SQLDelight. ### Source excerpt The convergence of iOS and Android development ## How We Develop New Features Using Offsites and Clean Architecture DevFeed: [How We Develop New Features Using Offsites and Clean Architecture]() Original publisher: [Read original article]() Published: 2018-11-02T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Architecture & Design](), [iOS](), [Swift](), [Objective-C](), [mvc](), [App]() Tags: [app](), [apple](), [architecture](), [bug](), [code](), [engineering](), [ios](), [mvc](), [new-feature](), [swift]() ### AI overview SoundCloud describes how its iOS team developed new features while modernizing a large legacy codebase containing Objective-C and Swift. The team adopted the VIPER architectural pattern, compared with MVC, and used it successfully for the Mini Player and later features. The article also explains how project kickoffs and focused offsites support feature planning, brainstorming, and team productivity. ### Source excerpt The current SoundCloud iOS App was built back in 2014, resulting in a huge codebase consisting of both Objective-C and Swift, with multiple... ## Delegates vs Closure Callbacks DevFeed: [Delegates vs Closure Callbacks]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2018-08-16T00:00:00Z Content type: comparison Language: en Sources: [Steve Barnegren]() Topics: [Swift](), [Objective-C]() Tags: [callback](), [closure](), [compare](), [delegates](), [objective-c](), [patterns](), [swift]() ### AI overview This comparison examines delegate and closure callback patterns in Swift, focusing on retain-cycle handling and managing callbacks from multiple instances. It finds delegates safer for weak-reference relationships, while closure callbacks are clearer when separating callbacks for multiple instances. ### Source excerpt Remember how awesome the delegate pattern was in Objective-C? Enabling classes to be super reusable by delegating out the bits that you might want control over. There's a reason that it's so ubiquitous across Cocoa Touch, it's just so damn good! ## Artisanal Objective-C Sum Types DevFeed: [Artisanal Objective-C Sum Types]() Original publisher: [Read original article]() Author: Heath Borders Published: 2018-05-14T18:49:35Z Content type: tutorial Language: en Sources: [Twitch]() Topics: [Objective-C](), [enum](), [C](), [Swift]() Tags: [c](), [engineering](), [enum](), [implementation](), [ios](), [objective-c](), [swift](), [twitch](), [types]() ### AI overview The article explains how to represent sum types in Objective-C. It contrasts Swift enums and C unions with enums, then presents a class-based, callback-driven approach for modeling distinct Objective-C object types under ARC. ### Source excerpt A sum type combines many possible differently-typed values into a single value, expressed in Swift as an enum. https://medium.com/media/6217cfe231386e04ce2e7228080fae7a/href In C, we can achieve the power of Swift's enum with a combination of a C union and a C enum: https://medium.com/media/3f1696d38fcec2600a942ffbe03c8cd4/href First, I'm sure you notice Swift's enum is more concise, but it's also safer. In C, the compiler doesn't prevent us from either creating an example with a mismatched type or from consuming a union as a mismatched type: https://medium.com/media/82f0586deab20a07abc615a9e459028e/href Trying to mismatch our enum types in Swift won't compile. Yay! https://medium.com/media/03d37cc33364b48d851beb4ccf38a97d/href Unfortunately, in Objective-C, we can't use Objective-C objects in structs or unions in ARC, so we can't use our C sum type with Objective-C objects. However, we can build a similar construct by hand. First, we need a class to capture all of the distinct types, and expose them through a single block-based callback interface: https://medium.com/media/78216b190ad6501c26ad89d0864b1c5c/href We must declare forward references for our distinct types, which we'll define later. We mark new and init as NS_UNAVAILABLE so that consumers won't be able to instantiate our base class directly. If they use -Wobjc-designated-initializers, they won't be able to subclass our base class either (without importing ExamplePrivate.h, which we won't distribute to them). Next, we'll declare our distinct types: https://medium.com/media/329743de725ccd196c3f535306714cf9/hrefhttps://medium.com/media/1785598f614b3963a0a39ec81d8c5dac/href They're simply plain-old-objective-c-objects that extend our base class. Our base class and our distinct types all have switchFoo:bar:. The distinct types will simply call the respective callback block with self. The base class will have an empty implementation. We use NS_REQUIRES_SUPER on switchFoo:bar: because if we add another distinct ## Build Native Interfaces - Camera Edition DevFeed: [Build Native Interfaces - Camera Edition]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-04-03T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Objective-C](), [Code](), [configuration]() Tags: [code](), [configuration](), [native](), [objective-c](), [tutorials]() ### AI overview A new course module explains how to build the Camera cn1lib and work with native interfaces. It covers Objective-C, callbacks, delegates, and configuration issues, providing broader guidance for native integration. ### Source excerpt I discussed the new Camera cn1lib last week. One of the motivations for doing it (besides the request from an enterprise account) was that of a new course module. Last week I added a new module covering the process of building the camera cn1lib... We have several online videos (both in the course and outside of it) covering native interfaces. So why do we need another one? Working with native code is error prone & complex. A lot of the tutorials we built in the past ended up spending more time on configuration issues than on code. In this module I talked a lot about Objective-C, callbacks, delegates & more. If you are thinking about native integration this helps give a more rounded view of the options. ## Meltdown and Spectre Server Updates and Codename One Feature Updates DevFeed: [Meltdown and Spectre Server Updates and Codename One Feature Updates]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-01-16T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Vulnerabilities](), [Server](), [IO](), [Objective-C](), [Java](), [iOS](), [Barcode](), [QR Code](), [simulator](), [API]() Tags: [announcement](), [api](), [blog](), [io](), [ios](), [java](), [objective-c](), [qr-code](), [servers](), [simulator](), [updates](), [vulnerabilities]() ### AI overview The post announces server updates in response to the Meltdown and Spectre chip vulnerabilities, with possible short-term downtime and limited expected impact on build speed because IO, rather than CPU speed, is the main bottleneck. It also mentions new Codename One libraries for Objective-C interoperability and Scandit barcode and QR code scanning, plus a push notification simulator feature. ### Source excerpt I've been so busy I just don't have time to blog as much as I should. I do hope next month will be better in this regard (more on that below) but right now I have to make an important announcement. There are new chip vulnerabilities I'm sure you heard a lot about specifically Meltdown & Spectre. Thankfully we are at a layer that shouldn't be impacted by these issues but we need to update our servers and will be doing so over the course of the next few days (possibly more as patches get updated). ## Friday Q&A 2017-10-27: Locks, Thread Safety, and Swift: 2017 Edition DevFeed: [Friday Q&A 2017-10-27: Locks, Thread Safety, and Swift: 2017 Edition]() Original publisher: [Read original article]() Author: Mike Ash Published: 2017-10-27T11:28:00Z Content type: article Language: en Sources: [Mike Ash]() Topics: [Swift](), [Concurrency](), [Deadlock](), [Objective-C]() Tags: [concurrent](), [deadlock](), [locks](), [mutex](), [objective-c](), [safety](), [swift](), [thread](), [threading](), [threads]() ### AI overview An updated guide to locks and thread safety in Swift, covering mutex types, their behavior, and related Apple and Objective-C synchronization facilities. ### Source excerpt Back in the dark ages of Swift 1, I wrote an article about locks and thread safety in Swift. The march of time has made it fairly obsolete, and reader Seth Willits suggested I update it for the modern age, so here it is! (Read More) ## Leveraging frameworks to speed up our development on iOS - Part 1 DevFeed: [Leveraging frameworks to speed up our development on iOS - Part 1]() Original publisher: [Read original article]() Published: 2017-10-16T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [iOS](), [Development](), [build times](), [build performance](), [Mobile](), [Architecture & Design](), [Scalability](), [Objective-C](), [Code](), [Swift](), [Cache](), [Git]() Tags: [architecture](), [building](), [code](), [development](), [git](), [ios](), [mobile](), [scalability](), [speed](), [swift](), [time](), [xcode]() ### AI overview SoundCloud describes how its growing iOS codebase developed long compile times, conflicts, and productivity problems. The team modularized the iOS project into modules with defined responsibilities and public interfaces, aiming to improve development speed and scalability. The article introduces the motivation and context for this modularization journey, including large targets, Objective-C and Swift code, CocoaPods dependencies, costly clean builds, and branch-switching overhead. ### Source excerpt Growth in code bases come with exciting scalability challenges. As the size of our iOS codebase and team at SoundCloud grew, we faced challenges: long compile times and conflicts. Our productivity started to suffer as a result. We took inspiration from the work done in the backend (Building Products at SoundCloud) and applied it to mobile development. The main goal was to get back to a state where development is fun, fast, and would scale as the number of contributors grew. We modularized our iOS project by splitting it up into modules with well-defined responsibilities and public interfaces that interconnect them. ## Friday Q&A 2017-10-06: Type-Safe User Defaults DevFeed: [Friday Q&A 2017-10-06: Type-Safe User Defaults]() Original publisher: [Read original article]() Author: Mike Ash Published: 2017-10-06T12:55:00Z Content type: tutorial Language: en Sources: [Mike Ash]() Topics: [Swift](), [Library](), [API](), [Objective-C](), [Vapor]() Tags: [2017](), [api](), [article](), [code](), [implementation](), [objective-c](), [swift]() ### AI overview This tutorial presents a type-safe Swift layer over NSUserDefaults. It describes typed keys, automatic key naming, default values, optional values, and conversion handled internally, with implementation examples. ### Source excerpt It's fun to re-imagine traditional techniques with a Swift twist. I've implemented a type-safe layer on top of the venerable NSUserDefaults, and I'm going to discuss my little library today. Credit/blame for this idea goes to local reader José Vazquez, although he inspired it by accident while talking about something else. (Read More) ## Doppl Sample Update - Kevin Galligan DevFeed: [Doppl Sample Update - Kevin Galligan]() Original publisher: [Read original article]() Published: 2017-10-04T15:00:55Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Android](), [RxJava](), [Gradle](), [Kotlin](), [Xcode](), [Objective-C]() Tags: [android](), [android-library](), [architecture](), [built-by-touchlab](), [code-sharing](), [dependencies](), [gradle](), [java](), [kotlin](), [objective-c](), [retrofit](), [rxjava](), [update](), [version](), [xcode]() ### AI overview A progress update on Touchlab's Doppl libraries and sample apps. The update covers compatibility work for J2objc 2.0.4, redeployed libraries, Party Clicker, reactive Room architecture code, and planned work on RxJava 2, Retrofit 2, Xcode support, the Gradle plugin, Architecture Components, and Kotlin. ### Source excerpt We're going through and updating Doppl libs & sample apps. For the next few months, we'll be working with 2.0.4 and locking down the libraries and versions. [Next page]()