I noticed in this project's README that you weren't sure about the DSL.
Well, what if we changed the DSL over to Android/Jetbrains Compose? It seems like fun idea because:
- Take advantage of the tree-building and reactivity built into compose
- Compose is gaining traction & mind-share, so this project might be more approachable by sharing concepts
- Improved code sharing; e.g. you could use
expect/actual to build common interfaces that work across both Android and native desktop.
- Jetbrains is already working on Compose Desktop, but some devs (myself included) disapprove of using Skia canvas instead of native platform widgets for reasons of accessibility/etc.. Plus, it's on the JVM and not Kotlin/native. So we could create a nice alternative to fill a different niche.
I'm just brainstorming, but I'm hoping to have some time to explore this myself, thought the idea was worth sharing.
I noticed in this project's README that you weren't sure about the DSL.
Well, what if we changed the DSL over to Android/Jetbrains Compose? It seems like fun idea because:
expect/actualto build common interfaces that work across both Android and native desktop.I'm just brainstorming, but I'm hoping to have some time to explore this myself, thought the idea was worth sharing.