The latest articles on DEV Community by Dakota Griffin (@dakotaruns). https://dev.to/dakotaruns https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211018%2F551b20a1-d4e6-4241-b5c6-e8bbe17a47ac.jpg https://dev.to/dakotaruns en Dakota Griffin Tue, 27 Oct 2026 15:25:48 +0000 https://dev.to/dakotaruns/kotlin-multiplatform-the-migration-i-wish-id-planned-27ee https://dev.to/dakotaruns/kotlin-multiplatform-the-migration-i-wish-id-planned-27ee <p>We started moving a shared business layer to Kotlin Multiplatform, and it's going well — but I'd do a few things differently.</p> <p>What I'd plan first:</p> <ul> <li>A clear boundary between shared logic and platform UI (we blurred it early)</li> <li>Dependency injection that works on both sides from day one</li> <li>A test strategy before the first shared module</li> </ul> <p>The wins are real: one place for models, serialization, and validation. The trap is thinking "shared" means "everything."</p> <p>Next milestone is sharing some of the state management. If you've done KMP on a real app, I'd like to hear what bit you.</p> kotlin mobile multiplatform