The latest articles on DEV Community by Cameron Hayden (@hayden_86). https://dev.to/hayden_86 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%2F4211037%2F3694b3d9-ec66-4c0b-8cfe-d971d2f5a36f.jpg https://dev.to/hayden_86 en Cameron Hayden Tue, 27 Oct 2026 15:52:14 +0000 https://dev.to/hayden_86/kmp-on-a-real-app-the-first-shared-module-59ba https://dev.to/hayden_86/kmp-on-a-real-app-the-first-shared-module-59ba <p>We just shipped our first Kotlin Multiplatform module in a real app. It's small — models, validation, and a bit of networking — but it's in production.</p> <p>What I'd tell someone starting:</p> <ul> <li>Start with a module that has no UI dependencies</li> <li>Write the tests in shared code from day one</li> <li>Keep platform-specific code behind interfaces, not <code>expect/actual</code> everywhere</li> </ul> <p>The biggest win was validation: one implementation, same behavior on both platforms, one place to fix bugs.</p> <p>The biggest surprise was build times. They're noticeable, and they add up in CI.</p> <p>Next step is sharing some state-management logic. I'm being cautious about that one — UI-adjacent code is where shared modules get messy.</p> kotlin mobile multiplatform