Yeah what they are trying to achieve is amazing, but they are failing on lots of small things which is overshadowing their successes.
I went down the path of creating flows as functions rather than having flows that would be running for days or weeks at a time and would have multiple branches etc. My reasoning for this was purely because of a few little issues that caused flows to break or not function properly. I had seen post after post of a microsoft support tech saying just re-create the flow from scratch, also telling you not to copy anything from your existing flow in case that pulls in anything that is broken (bearing in mind some people had huge flows that had taken them days to create)
Arguably I shouldn't be using an infantile language to develop projects and should wait a year or two until it's more rounded and a fuller product.
What sort of apps are you creating with it out of curiosity? With very basic apps it works wonders, but any time I want to do something more complex I feel that id be better suited creating something in .Net
A prime example of this is my first project was fairly simple and used a SharePoint list and I didn't have too many issues bar lack of experience with the language and update issues like we have faced today.
Then I moved onto a sql database for my second project because I couldn't find a way to granularly protect the data in the SharePoint list.
I was asked to add attachments to the second sql project to which I thought, sure no problem that's something you can do in any language (ive also used attachments in the SharePoint list) but unless you are using a sharepoint list you can't add attachments (easily) I have since found a solution for this which can only be described as hacky at best.
You have to add an image per attachment to your app and then you need to assign the value of the attachments to the image so you can get the blob data from the image and then pass it to a flow to create the file from the blob. By this point we were way beyond powerapps selling point of being incredibly simple, I also view being able to attach a file to your app a "simple" task that should be created out of the box as a function.
Instead it took weeks of dedicated to powerapps users' time to come up with a solution... Shout out to Shane Young and powerapps911 for producing some top quality videos, without them and without his attachments video my project would of been dead in the water and sent to the bin.
