Showing results for 
Search instead for 
Did you mean: 

PowerApps builder in Visual Studio

Would love to see the ability to design PowerApps forms in Visual Studio or something similar - would be great for editing more advanced/complex forms, and have the ability to set up the design surface that best suits individual designers.  It would also give us a decent code editor.  The whole "Office UI" paradigm (with the "File" backstage) is great for Word and Excel, but clunky and not really developer friendly.

Status: New
New Member

Yes, PowerApps builder in Visual Studio is a must for developing high-end complex form designs that's never possible with the existing UI design. This will provide great boost for Visual Studio and PowerApps both.

Not applicable

That's probably never going to happen given the audience for powerapps is the power user/citzen developer. 


Have you looked at Azure Logic Apps in Visual Studio? PowerApps is Azure Logic Apps under the hood, so is kind of the "complex" powerapps you're asking for already.

Advocate II

I agree with this post. I am not a software developer by trade, but I am building pretty complex apps and would LOVE if I didn't have to use the PowerApps UI. It gets very slow with not much complexity. It ignores key strokes while its "thinking" which is does every half second or so. I end up typing something like:




PowerApps will show that text, but there will be errors evaluated. Being naturally confused, I'll go looking elsewhere for the problem. Only to come back to the field and find that it only took:




Leaving off the rest of what I typed because the UI interrupted my keystrokes. VERY ANNOYING.


Perhaps, like Excel, there could be a "Application.Calculation = false" option so I can manually refresh the calculation in the app while I'm building. This would make life SO much easier in PowerApps.

Not applicable

Why anyone uses the visual studio to develop anything for PowerApps? Point of the PowerApps to move away from Visual Studio to develop business applications! 

Not applicable

I agree.  In the 1990s, MS created Visual Basic that had two audiences - the non-developer who could build working apps with little or no code.  Some of the components were not that efficient (such as the Data Control), but worked fine for a user utility.


The other audience was professional developers.  By dragging and dropping the basic UI elements, code could be used to determine how they were used, call out to libraries, or call into the Win16 or Win32 API.  This allowed developers to separate  concerns (then called n-tier) for making distributed apps.  So the concept of "no-code, low code" is nothing new).


Unlike the days at MS when Alan Cooper and others understood the pivotal role UI designers played in rapid application development (and thus lower SDLC costs), today's generation of "script kiddies" at Microsoft  just do not get the concept and its implication.