Taking a look at the `compose.web.widgets` source ...
# compose-web
c
Taking a look at the
compose.web.widgets
source code, it is very bare at the moment (a few types of buttons/text, but no TextField etc). At the moment, is the recommended way to write multiplatform UIs? Is it to stick with it and expect-actual what it doesn't have, or completely ignore it?
b
Compose is NOT flutrer. Ui code sharing is far from its main goals.
c
What's the point on doing on top of Multiplatform, then?
b
To allow sharing business, networking, persistence and view models
Basically 80% of your app
Here's an example to illustrate how mpp compose can be useful without sharing ui https://github.com/mpetuska/kamp/blob/feature/compose/app/client/src/commonMain/kotlin/util/compose.kt
c
Compose itself doesn't need to be multiplatform for that. If the goal isn't to share UI, why did they keep everything binary compatible between Android and desktop, using the same package names etc?