Building multiplatform apps requires thinking about architecture a little differently than their single platform counterparts. Individually, each platform has their own norms and customs, but they aren't alway a good fit to be shared with others. Often, they have coupled relationships with the platforms for which they were designed that don't play nicely with others. Over the past several months, Ryan Harter has been migrating the Chicago Roboto app from a Kotlin first Android app to a multiplatform app, and he has learned a lot about things that work well for one platform but not the other, and how to make those feel a bit more native. You'll learn about where to start the multiplatform conversion, adapting native libraries, communicating between shared Kotlin code and native platforms, and designing systems that non-Kotlin developers can get behind.