molecule VS iosched

Meanwhile, https://github.com/cashapp/molecule and https://github.com/slackhq/circuit/blob/cfcb6e6a28c53c0715d961917a9a5a9ddc07d5f3/docs/presenter.md?plain=1#L18

Reddit uses Molecule, not Circuit.

You could look at Compose, how the Compose compiler works internally, and perhaps build something unique / non-ui or investigate some other deep aspect of Compose compiler.

Thanks for the links, I already opened a bug issue : https://github.com/cashapp/molecule/issues/136

Today in "HN never used a reactive framework that is not React and is offended when UI is not written with Dear ImGui".

This is literally the exact style of SwiftUI and Jetpack Compose (down to the author having used the term fragment, I sure hope this isn't leftover trauma from being an Android developer), except written in Rust (hence having to deal with lifetimes in the middle, default parameters, lambdas being quite verbose and needing to move things, etc).

Not blocking the UI thread is mandatory if you ever want to make any kind of complex UI. If you're a web dev, well you only have one thread anyways, good luck, if you're on any other platform, interactions _cannot_ ever block the UI (unless you, yourself, update the UI to say it is blocked). Making this async is a good thing.

Stack traces are a problem, but then again they've been a problem in any remotely capable UI toolkit.

With ReactiveCell, it looks surprisingly similar to what Compose does, where modifying a State causes recomposition of everything observing it. Which means that it might be powerful enough one day to do the same things as Molecule (https://github.com/cashapp/molecule), or ComposePPT (https://github.com/fgiris/composePPT), where everything is a potential target and it interops really well with existing toolkits.

Hmm, I see 0.4.0 https://github.com/cashapp/molecule/releases/tag/0.4.0

Here's an example: https://github.com/cashapp/molecule

Recently, Cash App introduced Molecule and suggested that Jetpack Compose can help solve the problem of managing UI state.

This project has a history, before the next major changes, I moved to a single activity, also I modularized the features before I followed one shared module, and two modules to support the mobile and the TV look here , for now, I'm targeting the mobile, after some customization for tablet, then I will try to target the TV, so maybe you will find some code from the previous solution like this module, which is no need for now as everything is modularized. thanks :)

I feel like everything I do is RecyclerView's (or now, Lazy Grids with Compose 😅) so definitely check out the more popular UI elements like that. Also poke around in Google's classic I/O app which will show standard practices they push on the industry.

google/iosched was worse :D

Google iosched app uses a good pattern for creating binders which maps between x.class to ViewBinder and ViewBinder to layout or ViewHolder as you can see here.

In the Google I/O, there is a comment in a lazy initialization of Shared Prefs:

You want https://github.com/google/iosched/tree/b428d2be4bb96bd423e47cb709c906ce5d02150f/mobile/src/main/java/com/google/samples/apps/iosched and https://github.com/google/iosched/tree/b428d2be4bb96bd423e47cb709c906ce5d02150f/shared/src/main