Ever since Power Apps Component Framework went into the GA, there probably was not a day when a new PCF component would not be released by somebody in the Power Platform community.
There is just no way to ignore the fact that PCF has turned into a very popular addition to the Power Platform developer toolset.
And it’s not like it’s just a toy for developers to play with – in these few months I personally saw a few situations where PCF components were developed on the actual projects because they do provide the best level of re-usability and/or configurability when it comes to the UI components in Power Apps.
However, there is something very unique about PCF component development which makes it difficult to clearly answer the question of whether it’s complicated or not.
That may seem like a lot, but it’s, really, not.
Any plugin developer will tell you that the number of things one needs to learn to efficiently develop plugins is, likely, even greater.
Still, I’ve done PCF development, and I’ve done plugin development. If you ask me, PCF component development is way more complicated. Although, if you ask a seasoned front-end developer, they’ll probably say PCF is the most simple thing they had to learn lately.
Here is how I see PCF development:
In the same way, plugin development looks like this:
In general, it may take longer to figure out “plugin development framework”, but, once you’ve learned it, you can rely on your C#/.NET development experience to start creating useful plugins.
If, however, the answer is “no idea – I thought PCF would take care of it”, that’s where you’ll quickly find out that PCF is not a magic bullet, and you may still need to learn front-end development first.
And that’s when you decide if PCF is complicated or not…