onyxia-ui VS react-starter-kit

My advice if you don't have a multi-million budget and you only need to support React is to start from MUI components. Components like Date pickers, or Autocomplete are complex and time consuming to code from scratch. First thing you want to do is to build a custom theme for MUI (example DSFR, Example OnyxiaUI) this will make the MUI components roughly match your design system out of the box. Then you can create your own components that are wrapper around MUI components and customize them until they match your design (Example). Trust me, we always underestimate the complexity of building base component from scratch. There are tons of things to consider, I don't even mention the accessibility concerns... Customizing MUI components is the quick win route.

Shameless plug of our design toolkit: onyxia-ui. But it's good!

We are working on a UI toolkit that let you define what is the expected screen size. If you put 1920 for example and the screen is bigger than that it will stretch everything up. If the screen is smaller it shrinks everything down. It's not a perfect solution but it garanties that your app will look exactly the same no matter the screen size of your users. You can check it out here

Actually we are working on an alternative typescript first ui toolkit. tss-react is part of it. You can check it out it's onyxia-ui it rocks. It's still under active development but it's usable already. Also what's cool about it is that our salary are paid by the French tax payer so it's MIT, no strings attached.

Your Feedback Matters Your feedback is crucial for the continuous improvement of the React Starter Kit. Please try out the new version and share your thoughts and experiences. If you encounter any issues or have suggestions, feel free to open an issue on GitHub or join our community chat on Discord. We're excited to see the amazing applications you'll build with these new features! Happy coding! https://github.com/kriasoft/react-starter-kit

Part-time can be a great fit for developers who use their own stack and stick to a consistent architecture across multiple projects. For instance, I personally begin each of my projects with the same template (https://github.com/kriasoft/react-starter-kit 23k). This approach reduces overhead when juggling multiple tasks, allowing me to seamlessly make changes in one place and effortlessly push and merge updates into various upstream repositories for different clients. Excited about this efficiency-boosting method? Check out my new blog post where I delve into the details: https://medium.com/@koistya/enabling-efficient-front-end-dev.... Good luck with your project!

https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)

I like Joy UI library by Material UI team, while Material UI and Mantine, would be my 2nd and 3rd options respectively. Check out the list of UI libraries for React in this thread.

I don't have much experience with Next.js. But since most of my projects are CRM-like applications, I find Vite works really great for that type of apps. I'm bootstrapping new projects with the React Starter Kit template (pre-configured with React, Material UI, Vite, Google Cloud Identity, and Cloudflare Workers).

4 React Starter Kit React Starter Kit The React library, which has 20.6k stars, served as the foundation for Kriasoft's isomorphic starter kit. Modern web development tools including Node.js, Express, GraphQL, Babel, PostCSS, Webpack, and Browsersync are used by React Starter Kit

Vite in combination with Cloudflare Workers (for edge deployment) can be a solid default. See React Starter Kit as an example.