My first point, which I elaborated on in another reply to my comment, is that this makes sense for tools that are completely no-code. Refine brags about being d

My first point, which I elaborated on in another reply to my comment, is that this makes sense for tools that are completely no-code. Refine brags about being developer first. Their example on github is a 75 line React-ish script. So, someone is writing, testing, deploying code. If that isn't your dev team, then who is managing that process and supporting it when someone inevitably borks it? My second point is that even no-code tools tend to require developer support sooner or later. What I've noticed for admin tooling is that it often works best when it is driven by the product team. For example, customer support requests comes in which requires devs to stop working, investigate the issue, manually fix up data where necessary, etc. Devs hate doing this. Give the dev the ability to add the functionality to the admin and they often will, just to make the support requests go away. If you take away the admin from the product team then there is more friction in this path. I will admit however, that the quality of life improvements demanded by the support teams often go un-attended. But I don't see how Refine will help this go away if it requires someone familiar with next.js/React, Ant/MaterialUI, etc. to make changes.