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.