I gave it a try a few months ago, it seemed fine but ultimately opted against investigating further. It was cool being able to hook up my GraphQL API, but it fe

I gave it a try a few months ago, it seemed fine but ultimately opted against investigating further. It was cool being able to hook up my GraphQL API, but it felt slow and clunky, and didn't really meet my needs. It's obviously more modern, but you can achieve a lot of the same things with Microsoft Access or Filemaker (remember those?). There seems to be a bad assumption in the article, which is that working on backoffices is tedious. I actually enjoy it, building bespoke productivity tools for your own colleagues is interesting work. The more common issue is that it's often painfully difficult to get a company to agree to invest engineering effort in something they think they can just buy. So most backoffices just end up being a rushed pile of CRUD screens without any real design consideration. I think one solution here is to actually have a PM for backoffices, and invest in doing it well, rather than treating them as a technical burden.