Have you ever tried to convince an iOS developer or a JavaScript developer to try Kotlin for their main language or for major components of their app? Ha! That’s a fun conversation …

Why would people at large want to consider it outside of mobile

Through the JVM, you'd be able to share business logic between backend and frontend to improve or enable a frontend's offline behavior

you'd be able to share business logic between backend and frontend

but it has considerably

WASM exists as a KMP target because of Compose pretty much, that's the main purpose.

@Composable
internal actual fun SettingsView(viewModel: SettingsViewModel) {
    UIKitView(
        factory = {
            println("Calling settingsViewFactory")
            SwiftUiFactoryFinder.settingsViewFactory(viewModel)
        },
        modifier = Modifier,
    )
}

I saw this article the other day, and gave up reading...

undefined

I can confirm it is not a great App, that 💯, although it covers the basics for an e-commerce , perhaps is all they need

SKIE helps a lot, but with the plethora of various libraries (KMP-NativeCoroutines, KMP-ViewModel, MVIKotlin, Orbit, etc etc) makes it very confusing to figure out how you should be doing this.

But the interface tools you have is going to affect the architecture you adopt.

or example, my biggest issue currently is that I have these view models that inherit from an abstract class which specifics generics for its state and side effects. But when you bring those over in Obj-C, you can’t make that conform to Swift protocols that specify associated types because of runtime type erasure.

public interface ContainerHost<STATE : Any, SIDE_EFFECT : Any> { ... }
class MyViewState 
class MyViewSideEffect
class MyViewModel: ContainerHost<MyViewState, MyViewSideEffect> { ... }

ObservableObject

public abstract class ViewModelContainerHost<STATE : Any, SIDE_EFFECT : Any>: ContainerHost { 
    var nativeStateFlow
      get() = container.stateFlow.asNativeFlow() // KMP-NativeCoroutines
    var nativeStateValue
      get() = container.stateFlow.value
}

protocol Store<State, SideEffect> {
    associatedtype State
    var state: CurrentValueRelay<State> { get }
    
    associatedtype SideEffect
    var sideEffect: AnyPublisher<SideEffect, Never> { get }
}
// Some other things adapting Store to ObservableObject...

extension ViewModelContainerHost: Store {
    typealias State = STATE // ERROR
}