PowerApps are great and really easy to build. They however can get complicated quickly. This session is about starting a conversation about what we can do when we are building a PowerApp so it can be managed and scaled so the PowerApps you build can become a reliable part of any system.
In this session I would like to present and discuss PowerApps Canvas App Development Standards. Drawing on my experience listing a Canvas App in the Microsoft Partner Showcase, building numerous other Canvas Apps, and the Microsoft PowerApps Canvas App Coding Standards and Guidelines White Paper I’d like to present a framework or approach for developing Canvas Apps so they can be built and maintained sustainably. From simple naming conventions through to code organization, performance optimization and other tips and tricks I will explain how a Citizen Developer with no background in DevOps can build and maintain apps in the context of large and complicated IT system. Attendees with no PowerApps experience will learn about the common pitfalls of software development in a PowerApps context, and how to avoid them, while experienced developers (myself included) will benefit from a reminder of what makes building software easier and what can make it much much harder.
What’s a bad citizen developer?
How bad can it be?
So it can be painful, what can we do to avoid it?
Measure Twice, Cut one (Plan, Plan, Plan..)
What does planning look like for a PowerApp?
Naming Conventions are not that boring
Styling, Configuring and Documenting behind the scenes
Code organisation (where to put it, how to chain ifs, formula differences compared to excel)
And finally, make sure you know what you are actually doing…
16:20 - 17:10