{"id":14063,"date":"2021-10-13T07:00:00","date_gmt":"2021-10-13T11:00:00","guid":{"rendered":"https:\/\/centricconsulting.com\/post\/powerapps-development-strategies-part-1_portal\/"},"modified":"2023-07-26T15:31:10","modified_gmt":"2023-07-26T19:31:10","slug":"powerapps-development-strategies-part-1_portal","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/powerapps-development-strategies-part-1_portal\/","title":{"rendered":"Power Apps Development Strategies"},"content":{"rendered":"
Microsoft<\/a> has done a fantastic job of encouraging organizations to explore Power Apps development. And if you’re reading this, either you’re interested in Power Apps<\/a>, or one of your business users created a Power App that is now critical to the company, and it is now yours to manage.<\/p>\n I’ve spoken to many organizations that have started asking their business users to create their own Power Apps. However, those organizations often end up with developers sharing Power Apps across the organization that becomes critical to users.<\/strong> But, the business users who created the apps had no guidance, governance or cohesive strategy for designing and maintaining their creations.<\/p>\n So, what should you do to get a handle on these Power Apps? Or to prevent this from happening in the first place?<\/p>\n Don’t let that title scare you. For smaller organizations, this may be one or two people. For larger organizations, it may roll into a larger, defined program management office<\/a> (PMO), but the goal here is to have a single point for guidelines and for the governance of Power Apps design and management.<\/p>\n This group should provide:<\/strong><\/p>\n Colors, icons, fonts, form factors \u2013 Oh, my! You have a lot to consider, but by providing end-users with a consistent experience across your Power Apps, you can ensure a positive experience and decrease support and training costs as you maintain and deploy new apps. You also should decide which form factors you intend to support.<\/strong> Remember, Power Apps is not responsive, so deciding to support either phone or tablet \u2013 or both \u2013 will determine how you plan the development time for each.<\/p>\n Power Apps security is a fairly simplistic process. Users can either create or use apps shared with them. Plan different groups to make the management of sharing apps much easier. Use data access policies to ensure that users only use approved data sources in Power Apps when accessing business content. Define these policies from the outset to prevent data leakage. Consider augmenting Power Apps with Intune Mobile Application Management<\/a> to add an additional layer of security for mobile users.<\/strong><\/p>\n As soon as your end-users understand they might be able to get their custom processes, the floodgates to requests will open. From new projects to feature requests, you should have a way for users to communicate what they need and the time frame they need it in.<\/strong> This becomes a meaningful way to manage and prioritize how you can meet their needs. You can use many tools for this step, such as using a particular platform to create your own.<\/p>\nBegin With a Power Apps PMO<\/h2>\n
UI\/UX Guidelines<\/h3>\n
Security<\/h3>\n
Demand Management<\/h3>\n
Change Management<\/h3>\n