I've been working on this project since 2019 (back when it was called idom) and before that in a prior ill-fated iteration from 2018. I don't expect that to change any time soon.

With respect to MaterialUI, there are two main areas of friction I can foresee:

• The first is around passing children to components that are implemented in JS since the children are passed as VDOM elements rather than rendered ones. I've been thinking about some ways to make this easier, but it hasn't been high on the list of priorities since no one has asked about it. If you're interested, this is something that I could take time to work on and document.
• The second relates to the fact that (I think) in some places MUI passes components as props. This is also likely solveable, but I haven't put enough thought into it to have any concrete ideas there.

I've been helping out with this project since 2021.

I similarly long term plans for maintenance of the following:

• reactpy-django
• Advertising and branding
• Technical and design direction

And upcoming tasks I'm adopting:

• reactpy-router
• reactpy-build
• ReactPy documentation

@rmorshea and @Archmonger , it's great to see so much enthusiasm from you two to make this project a success. My experience so far (one day only) with ReactPy has been quite positive. I'll try to investigate using MaterialUI with ReactPy in my spare time and tell you about my experience (and suggestions on what could be changed in ReactPy to make this process easier).

Hello there,
Would be also very curious about MUI support.
Great work, thanks a lot! Am starting to play with it.