Roman Kamyshnikov

🚀 Kotlin 2.2.20-Beta2 introduces experimental support for Swift export 🎯 No more Objective-C headers! You can now call Kotlin code directly from Swift in a clean, idiomatic way – a big win for Apple multiplatform development 🍏 🧩 What’s new: - Multi-module export as separate Swift modules - Kotlin packages preserved to avoid naming conflicts - Support for typealias and overloaded functions - Improved nullability for primitives - Flattened and customizable package/module structure Huge step forward for Kotlin Multiplatform Mobile (KMM) developers! 💪 https://lnkd.in/d34vyFZj #Kotlin #Swift #KMP #KotlinMultiplatform #AndroidDev #iOSDev

59

Android engineers just got the fastest coding agent (Qwen-3-coder-480b)! 2.5x faster than sonnet 4 with near similar performance: - We had to adjust the tool calling / prompts to make this model behave correctly - Can swap out the agent by clicking a button Here is one of the samples from our blog, where both agents race to implement a UI change given zero code hints and just a visual description: "swap the emoji and picture button in chat input box"

96

6 Comments

🚀 Core Data vs SwiftData: What iOS Developers Should Know For years, Core Data has been Apple’s go-to persistence framework. It’s powerful but also… verbose. Setting up models, contexts, and boilerplate often felt heavy, especially for smaller apps. With iOS 17, Apple introduced SwiftData — built directly on top of Core Data but with a modern, Swift-native approach. Think of it as Core Data re-imagined for the Swift era. ⚠️ Important Note: SwiftData is still new. Under the hood, it’s Core Data with a modern API, which means migration from Core Data is possible but not automatic. For enterprise-level, battle-tested apps, many teams are still sticking with Core Data for now. cc : Mobile Innovation Network #iOS #tech #uae #software #developer #opponents #linkedin #creator

248

10 Comments

Expo SDK 54 introduced React Native precompilation, cutting uncached iOS build times by almost 10x. This is a big improvement, but testing with a larger app (80 dependencies) shows there’s still room to make builds even faster—possibly another 2x. Take a look at the chart for details. #ReactNative #Expo #iOSDevelopment #IOS #RN #Development #Performance #React #Development #MobileDevelopment #App #JS #DevTools #JavaScript #AppDevelopment

140

1 Comment

How to go from Junior Developer to an Android Staff Engineer? I recently talked with Kyriakos Georgiopoulos, who works as an Android Staff Engineer at Skroutz. We will be discussing: - How does he mentor Junior developers? - What does a Staff Engineer actually do? Link below: #android #kotlin #jetpackcompose #ios #androidapp #app #apps

74

4 Comments

🌍 Kotlin Multiplatform (KMP) is the future of cross-platform development — and I just published my first ever Medium article on how to modularize a real-world KMP project! 🎉 📖 In this guide, I break down: ✅ How to structure a multi-module KMP project ✅ Building shared frameworks for Android & iOS ✅ Clean architecture with features, data, domain, and UI layers ✅ Real-world project example + GitHub repo Whether you’re an Android dev stepping into KMP or an iOS engineer curious about shared code, this article gives you a complete roadmap with practical code samples. 👉 Read the full article here: https://lnkd.in/dp88tkJW 🔗 KMP Modularization — Ultimate Guide with Real World App 💬 I’d love to hear your thoughts — do you see KMP shaping the future of your projects? #Kotlin #KMP #JetpackCompose #AndroidDevelopment #iOSDevelopment #MobileDevelopment #CrossPlatform

35

🚀 Swift Evolution: `weak let` is now officially accepted! Great news for Swift developers - SE-0481 has been accepted, allowing us to combine `weak` with `let` for the first time! The problem we had: final class MyClass: Sendable {   weak var delegate: Delegate? // ❌ Error: mutable property in Sendable class } What will be possible soon: final class MyClass: Sendable {   weak let delegate: Delegate? // ✅ Works perfectly! } Why This Matters: • Cleaner concurrency code - Classes with weak references can now be Sendable. • Better closure captures - @Sendable closures can use weak captures without workarounds. • Conceptual clarity - A weak reference becoming nil isn't really a "mutation". Key Insight: The restriction was based on thinking that weak references "mutate" when objects are destroyed. In reality, the reference stays the same - we just can't observe the object anymore. This removes a major friction point in Swift's concurrency model while maintaining all safety guarantees. No more wrapper structs or complex workarounds needed! Swift Proposal: https://lnkd.in/dQDbjSEC.

44