# multiplatform

Mofe Ejegi

10/24/2023, 1:21 AM
Hey everyone 👋 I’m about to commence working on a mobile application and I’ve decided to use Kotlin Multiplatform. My goal is to share business logic across both Android and iOS, and I’m leaning towards writing the UI natively for each platform (using Jetpack Compose for Android and SwiftUI for iOS). But the catch is…, I’m on a tight deadline and I’m the sole mobile engineer on the team. So I was wondering if anyone has had experience starting a project with Compose Multiplatform and eventually pivoted it to a Kotlin Multiplatform project (for example, after achieving an MVP). I appreciate any insights or advice on this. Thank you!

James Black

10/24/2023, 3:31 AM
The iOS version is alpha only so I would be nervous writing it and finding out there is something missing or some behavior that is causing you a problem. I would start with just write it in SwiftUI and Jetpack Compose and after you have your MVP then look to see if Compose Multiplatform would meet your needs.
💯 1

Landry Norris

10/24/2023, 5:11 PM
You could also start with Compose, since you'll need it anyways for Android. Then try to run on iOS and see if there's any issues with your use case. If there are, then write SwiftUI next. If not, keep it in compose for now. You likely won't care if there are breaking changes in compose multiplatform later, since you plan to move to SwiftUI later.

Mofe Ejegi

10/25/2023, 9:01 AM
Thank you both 🙏 I’ll start with Compose for this, and if I run into any issues, I’ll just take advantage of SwiftUI/Compose interoperability: