mosaic VS dioxus

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).

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI