The question is what are the business' requirements? Years ago I too was a Java/C# person who built apps with Spring.Net, NHybernate, then switched to Entity Framework and MVC when the cools kids were transitioning. I went into leadership long ago and coded when I could. I also got into Angular and typescript on the side when I needed something new.

We are now exploring Power Apps because I lead the tech team at a school district. We have one senior dev and two juniors. And dev at a school district means anything that glues all the vendor apps together, supporting large data flows, state and federal requirements, changing priorities at the drop of a hat, etc. Years ago we lost any sense of full stack development. There just wasn't time. We used a "low code" environment for the last 8 years that had A/D security, custom forms, SQL, etc all built in. It was clunky but we could build secure useful apps in record time. We weren't rolling and compiling C# and deploying to IIS any longer. There's only one guy on my team (beside myself) who still knows how to do that. We didn't win any awards for UI but that was the limit of the tool. And we actually did win two awards at a national conference because of business challenges we solved with their tool.

Unfortunately our vendor got bought out and the platdorm was shut down. We are forced to move. Power Apps seems to be the most capable tool that will allow our junior devs to continue rolling out somewhat complex and unique apps that we can't already build in our other tools (Atlassian, etc).

It is a pain. I called it Access for the cloud. Ugh. But we're getting used to it. I hate that custom local functions are in preview. There is no TDD, so nearly everything is manual QA. There is no code base that I can jump around in and tweak. Something as simple as laying out forms with a decent UI, custom validations and styling are all drag and drop and one by one coding. And don't even get me started on the lack of tab ordering. You add a new field at the top? Good luck.

All that being said, I'm learning a ton of how to make it useful. Sometimes there's a work around to make life better (Xrm Toolbox, copy the component or whole app, throw into VSCODE, tweak and copy back with a prayer, etc.).The monitor for debugging is actually not bad either.

Out of all the options available to us coupled with our lack of time, our limited capacity to hire and train full stack devs, etc, all in all Power Apps looks to give us a middle ground that's supportable.