Maxime Naulleau
1y ago
I built many frontends with React and had to improve the same things constantly.
I don't like frameworks that much. But in my search for a better frontend architecture, I found Refine. I adopted it pretty quickly.
Here are the 4 benefits I didn't find elsewhere.
🧵
1/7
Maxime Naulleau
1y ago
1. Headless approach
That's what makes Refine so enjoyable IMO.
You declare what you need in a React context and use its hooks. Just pick what you need and skip what doesn't interest you.
Their headless approach lets you choose between framework features and custom logic.
2/7
Maxime Naulleau
1y ago
2. Handle auth, CRUD, and more
Refine manages many things out of the box. First, you choose your providers. Then things like auth, permissions, or CRUD with filters will just work.
It does all this without making me lose too much flexibility in my code design.
3/7
Maxime Naulleau
1y ago
3. Infrastructure and domain separations
Refine's React context abstracts the implementation details of your providers. Its hooks let you develop components with business logic. This isn't exactly clean architecture, but a step toward it.
It helps to have a consistent codebase.
4/7
Maxime Naulleau
1y ago
4. DevTools to debug faster
DevTools are so handy that I mentioned this beta feature. For now, it's like the React Query DevTools customized for Refine. Because Refine abstracts many frontend features, I think this can become a game changer.
Can't wait for the alpha.
5/7
Maxime Naulleau
1y ago
If you liked this thread and are interested in SaaS, you can:
• share this thread
• or follow me at @MaximeNaulleau for more content. I publish 4x per week.
6/7
Maxime Naulleau
1y ago
The TL;DR:
Refine is a massive gain in React development time:
1. Headless approach
2. Handle auth, CRUD, and more
3. Infrastructure and domain separations
4. DevTools to debug faster
It's worth looking at @refine_dev if building a new SaaS.
7/7