meow VS mosaic

As you can see, cli.tsx also looks pretty similar to React's root file, but, it has something more to offer using meow library. meow is a popular library that helps you build nice CLI applications gives you access to create usage docs and handles args and flags.

You will notice that it is using meow to read the command and flags. Afterward, it passes the flags to the ui component and renders it. meow is a helper library to parse arguments. The text passed to meow() is the help text shown when you call create-micro-service --help.

Here the App component is being imported using a special importJSX command. Meow is a library that allows us to make interactive CLIs. Here look at the render statement. A React element is being created where the App Element is passed as the first argument (ie the JSX part of the element) and then cli.flags is an arrow of props that will be passed into the element. This is where the name prop is coming from!!!

One of favorite offshoots of compose is https://github.com/JakeWharton/mosaic, which is a tool to build TUI's. Is something that you plan for this library, basically making the targeted renderer plug-able?

There's also Mosaic, which is an experiment of sorts to build console UI using Kotlin and Jetpack Compose: https://github.com/JakeWharton/mosaic

Not sure if this is what you're looking for but it seems pretty cool: https://github.com/JakeWharton/mosaic

To see some non-Android examples of Compose, take a look at https://github.com/JakeWharton/mosaic

Have you tried either clikt or mosaic??

Mosaic

Would be really cool if one day this could be made to work with the compose compiler, kinda like compose for web, mosaic (compose for TUI apps), or another project that I can't find right now but it was basically compose with one of Apple's UI frameworks

Jetpack Compose (Google's alternative on Android, that also works pretty much anywhere you can run a JVM and others like the web [1], terminals[2], powerpoints[3], as well as pretty much anywhere you have an imperative API that you want to transform into a functional model[4]) is infinitely more polished and has better tools than anything Apple has put out in all of SwiftUI's existence. Apple is bringing this upon themselves with their "major updates" concept for SwiftUI coming every other year, where components aren't even available on old versions of iOS. A UI toolkit is a library like any other, version it like a library and match patch releases.

[1] https://compose-web.ui.pages.jetbrains.team/

[2] https://github.com/JakeWharton/mosaic

[3] https://github.com/fgiris/composePPT

[4] https://github.com/googlemaps/android-maps-compose

Compose itself can be used by pretty much anything then. There's Compose UI, there's Compose Multiplatform, that on the web targets the DOM, on Windows targets... WinUI or any component library ? and more. For example, you can have a terminal renderer with it: https://github.com/JakeWharton/mosaic. Or hell, even drive an iOS view (https://twitter.com/jakewharton/status/1399561083204026369). The way it works also allows transforming coroutines calls, which are asynchronous into basically synchronous components, without ever making use of the UI part (https://github.com/cashapp/molecule).