--- title: Mitigating the Risk of Siloed Native Code | daily.dev description: Engineering teams maintaining separate Android and iOS codebases face five key risks: duplicated development effort, feature drift between platforms, high... canonical: https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Mitigating the Risk of Siloed Native Code | daily.dev og:description: Engineering teams maintaining separate Android and iOS codebases face five key risks: duplicated development effort, feature drift between platforms, high... og:url: https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi og:image: https://api.daily.dev/og/posts/lOk6rznBI.png og:image:alt: Mitigating the Risk of Siloed Native Code og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Mitigating the Risk of Siloed Native Code **[Touchlab](https://daily.dev/sources/touchlab)** · 7 min read · 0 upvotes · 0 comments ## Summary Engineering teams maintaining separate Android and iOS codebases face five key risks: duplicated development effort, feature drift between platforms, high economic cost (35-50% of dev time on bug fixes), political pressure from management, and developer recruitment/retention challenges. Kotlin Multiplatform (KMP) is presented as a low-risk solution because it is optional and incrementally adoptable, natively integrates with both JVM and Xcode/Swift, avoids adding a third language ecosystem, and allows fallback to native code when needed. Unlike React Native or Flutter, KMP focuses on sharing non-UI business logic while keeping native UI intact. The post also announces Touchlab Share, a week-long webinar series covering multiplatform evaluation, code sharing candidates, KMP proof-of-concept building, and business case development. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Kotlin Multiplatform Is Not Cross-Platform: Understanding the Real Difference](https://daily.dev/posts/kotlin-multiplatform-is-not-cross-platform-understanding-the-real-difference-feksv6re1) · Medium · 0 upvotes · 0 comments - [Helping Decision-Makers Say Yes to Kotlin Multiplatform \(KMP\)](https://daily.dev/posts/helping-decision-makers-say-yes-to-kotlin-multiplatform-kmp--ts09b63zw) · JetBrains · 1 upvotes · 0 comments - [Why we love multiplatform with Kotlin and Compose](https://daily.dev/posts/why-we-love-multiplatform-with-kotlin-and-compose-ygw5twyaa) · Q42 Engineering · 0 upvotes · 0 comments - [Why We Chose KMP Over React Native: It’s an Architecture Bet, Not a Framework Preference](https://daily.dev/posts/why-we-chose-kmp-over-react-native-it-s-an-architecture-bet-not-a-framework-preference-gjuzubyyt) · Medium · 1 upvotes · 0 comments - [Compose Multiplatform Is a Business Decision, Not a Technical One](https://daily.dev/posts/compose-multiplatform-is-a-business-decision-not-a-technical-one-oo4sm9b4f) · Touchlab · 1 upvotes · 0 comments --- Tags: [#mobile](https://daily.dev/tags/mobile), [#android](https://daily.dev/tags/android), [#ios](https://daily.dev/tags/ios), [#kotlin](https://daily.dev/tags/kotlin) [View this post on daily.dev](https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Mitigating the Risk of Siloed Native Code","url":"https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi"},"datePublished":"2026-08-02T07:15:44.713Z","dateModified":"2026-08-02T07:42:52.082Z","description":"Engineering teams maintaining separate Android and iOS codebases face five key risks: duplicated development effort, feature drift between platforms, high...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a921620cd8855b36880009151f3ae0a5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a921620cd8855b36880009151f3ae0a5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Touchlab","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Touchlab","logo":"https://media.daily.dev/image/upload/s--CQ0u6GwB--/f_auto,q_auto/v1785654902/logos/touchlab?_a=BAMAMicg0","url":"https://daily.dev/sources/touchlab"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/mitigating-the-risk-of-siloed-native-code-lok6rznbi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,android,ios,kotlin","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Touchlab","item":"https://daily.dev/sources/touchlab"},{"@type":"ListItem","position":3,"name":"Mitigating the Risk of Siloed Native Code"}]} ```