<@UL1A5BA2X> <@U050W8F10RZ> I’m planning to start ...
# compose-web
p
@Big Chungus @Morten Minke I’m planning to start working on a simple Web app (an internal tool for my company) and I’m wondering to what extent your solutions (mpetuska/kmdc and mminke/kotlin-compose-web-material3) are stable and ready to be used in a product with medium level of importance. Or maybe there are other Compose-ready component libraries that you’d recommend?
b
There's also bootstrap-compose if you don't need material. KMDC is now feature-complete as it has wrappers for all mdc components. However it's not battle-tested yet. I'm happy to look into any bugs you might encounter if you do choose to go with it and battle test it for me. Also @rocketraman was using it for one of his internal projects I think.
p
thanks, I’ll talk to my teammate and let you know 👍
m
Kcwm3 depends on the work of the Google team developing the Web Components. It's still in alpha stage and there are likely breaking changes going to occur in the coming period. So I think KMDC would be a better option for now. Thx for at least considering and asking the question!
p
to be honest, for now I’m close to choosing the good old https://github.com/JetBrains/kotlin-wrappers/tree/master/kotlin-mui and staying with React because it has a table component and MUI generally looks more mature than material-components-web (correct me if I’m wrong)
wait: https://kmdc.petuska.dev/#/MDCDataTable - I must have missed because it’s called a data table, not just a table
b
It definitely is, plus it has much better docs. Main tradeoff is that you're forced into React