-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User research #58
Comments
Hi @oliviertassinari , we all love the wonderful MUI, but we have several concerns about UI libraries in this project:
The new project is still in early version, we are focusing on feature not UI library for now. And the decision is not final, we will try Base UI in the future. Thanks for your watching ❤️ |
@634750802 thanks for the answer; really appreciate it! Out of curiosity, were you aware that Base UI or even Joy UI (these two being alternative UI libraries developed by MUI) existed before Olivier's comment? 😬 |
@danilo-leal Yes, I found them on document site before. They are very suitable for MUI developers. For this project, Joy UI is in same situation as MUI and Base UI is lack of some components. Both of them are in beta version now so I didn't try. But I would like to try BaseUI + Tailwind CSS in my personal projects!🚀 🚀 ----- without next13 appdir 🤣 |
@634750802 Love it, thanks! So I hear:
|
I'm coming from https://ossinsight.io/ which is built on Material UI. We are using OSS Insight to create custom dashboards to monitor the work of the community on our open-source repositories: https://tools-public.mui.com/prod/pages/9r8fshsf. I have noticed that the next version will be based on Tailwind CSS + Radix, so dropping Material UI.
This feels like a great product feedback opportunity. I would love to learn more about the thought process for the change. What's the appeal? What made Base UI a nonviable option? Thanks!
The text was updated successfully, but these errors were encountered: