That said, we're currently focused on helping people build apps without code, so classic source control methods like git are not part of those near-term plans. There's some richer background on that in this discussion if you're interested in going deeper.
Empowering our users is a REALLY good idea, but the problem is I've had management tell me a few times that I need to learn how to write "code" with these platforms; and honestly, the experience has been highly frustrating. I've had situations where people have told me to write solutions in SharePoint, Power BI or Power Apps when it would be easier and cleaner to use C#/(Classic MVC) and/or SQL Server Reporting Services. That doesn't even begin to address the high potential cost of these user written apps.
Anyway, I applaud Microsoft for trying to make software development easier. I think most "professionals" and business people (even developers) want that, but I still find Power Apps a royal pain to use with a lack of perceived flexibility.
One simple thing Microsoft could do to make this better would be to improve the "code editor" that you use inside PowerApps events. For example, when I try to edit the OnSelect Action of a Button in PowerApps, I'm given this tiny little window to work with. For the kinds of solutions my institution needs, we are going to have to write more than a few lines of code for each action. Over time, this large volume of business rules is going to create a bunch of O365 Spaghetti Code that is very difficult to debug. To make matters worse, we will be stuck without a "debugger" and we will have to edit our code through tiny little "windows"...
Another thing Microsoft could do is maybe offer a client side tool for "development". The online editor is a bit sluggish in my personal opinion even when I'm onsite at the office.
BTW: Forgive me if I'm wrong on any of this. I'm just stating my frustration with getting quality non-trivial user focused "apps" out to the user given the tools built into the O365 subscription that my institution provides me.
 - SQL Server Reporting Services is another pretty easy option for visualization that is reasonably clean.
There was a session at Microsoft Build 2020 about this.
As I understand it (I was only just able to keep up!) it involves the use of a few different "Environments", then having the PowerApp packaged up in to a "Solution". You can use Visual Studio "Pipelines" to move the Solution between Dev/Test/Prod Environments.
The Power Automate Flow from @seadude may also be useful.
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
FIll out a quick form to claim your community user group member badge today!
Features releasing from October 2020 through March 2021