The Clearly Podcast

How to Approach a Power Apps Project

Summary

Power Apps and other low code/no code platforms are often seen as a quick and easy solution to allow users to solve their own problems.  But is it that simple?

What is the place for Power Apps, and if you decide to start a Power Apps project, how should you go about it?

This week, we discuss how to approach a Power Apps project, why you should take it seriously, and why you need to think about data structures.

Our main takeways this week are that Power Apps are software projects, and should be managed accordingly.  That you need think about the data, how it's stored, and how it's secured.  And you need to be mindful of what the platform does - and perhaps more importantly, what the platform doesn't do.

Chris can be found here: http://www.cpegroup.co.uk
You can download Power BI Desktop from here.

If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.

Transcript

Andy: Excited to have Chris, a former Microsoft colleague, on the podcast.

  • Chris: Background in software engineering, worked at Microsoft for 17 years, now an independent consultant focusing on Microsoft technologies.

Discussion on Power Apps

  • Andy: Many people think Power Apps can quickly solve all issues, but that's not the case. We want to provide guidance on approaching Power Apps projects.

  • Chris: Power Apps are built on the Dataverse platform, which evolved from Microsoft's Dynamics products. They offer flexibility for creating custom solutions.

History and Evolution of Power Apps

  • Chris: Power Apps started as part of Project Green by Microsoft to unify data backends. Now, Dataverse serves as the core platform.

  • Shailan: Dataverse, formerly Common Data Service (CDS), offers standard entities and connectors. Choosing between Dataverse and other options like Azure SQL depends on specific needs and costs.

Practical Use of Power Apps

  • Andy: Power Apps can complement other applications, fixing gaps or enhancing processes. For instance, using Power Apps to fill gaps in ERP systems.

  • Chris: Examples of using Power Apps to handle purchase order approvals, integrating various business processes.

Project Management and Approach

  • Chris: Importance of defining requirements, data models, and having a structured approach. Avoid letting users create unregulated apps without proper oversight.

  • Shailan: Emphasize control and boundaries to prevent security issues and ensure consistency. Use environments like dev, test, and prod to manage the lifecycle.

  • Tom: Benefits of close integration with user needs, ensuring apps match business processes.

Recommendations for Success

  1. Know the Platform: Understand what's in Power Apps and what's not to avoid unexpected costs.

  2. Start with the End in Mind: Define clear objectives and requirements before beginning development.

  3. Manage Complexity: Stay updated with the platform's roadmap and prepare for evolving features.

Conclusion

  • Chris: Encourages a structured approach to Power Apps projects, considering professional guidance when needed.

  • Andy, Shailan, Tom: Agree on the importance of documentation, proper planning, and managing user expectations.

Final Thoughts: Power Apps offer significant potential, but success depends on a thoughtful, managed approach. Engage experts and follow best practices to harness the full power of the platform.