/Building-a-Culture-of-Innovation-with-Low-Code

Frequently ask questions from the Fireside Chat: Building a Culture of Innovation with Low-Code and Fusion Development.

Building-a-Culture-of-Innovation-with-Low-Code

MS_2525_CDS_RegBanner_DevTools_1920x300 (1) Fusion Development brings together low-code and professional developers to further accelerate innovation at scale. Register now to learn how other organizations applied this approach to make better business decisions and develop new products and services.

Watch the session On-Demand here.

Frequently Asked Questions

Frequently ask questions from the Fireside Chat: Building a Culture of Innovation with Low-Code and Fusion Development.

Question Answer
What are some high-value and high-touch use cases that you've seen for wide adoption of Power Apps within an organization? There have been many great customer stories published at Microsoft Power Platform Stories Microsoft Power Apps. EY has had several public use cases, one for finance at eyzilla and another where they created a solution that handled billions of dollars in PPP loan applications.
Low-code doesn't mean no-code, so where and how can code be used in this system? Developers can incorporate code into many places in the platform - they can write custom UI components using common frameworks like Angular or React, and they can add .NET code to serve as event handlers or process complex logic via custom APIs or plugins.
Are the created apps centrally hosted by Microsoft Servers, or can they be deployed to a specified web host? Power Apps are SaaS applications, and so they exist fully in the Microsoft cloud.  However, these apps can be built to run offline on a Windows, iOS, or Android device.
What is the pricing plan? Is it per user? Per created application? Both? Power Apps has both user-based licensing as well as pay-as-you-go based on consumption. More details can be found on Pricing - Power Apps
What would be examples where you would NOT use Power Apps? Where it is not suitable, for instance? Power Apps don't cover every customer scenario, for instance if you want a native mobile app used by end customers, it wouldn't normally be a good fit.  That said, customers frequently compose solutions with a combination of low-code and pro-code, so it's not always a yes or no answer.
What sort of best practices do you see emerging for executing on devops, quality assurance and validation in a Fusion Development environment? We've published a fusion development e-book here: Ebook: Fusion development approach to building apps using Power Apps - Power Apps
Does this low-code system generate actual code that can then be modified?   Power Apps do have source files, which enable integration with source/version control services like GitHub and Azure DevOps, among others.  Developers can modify those files or work with them through our maker portals.