• No products in the cart.
View Cart
Subtotal: £0.00

Month: February 2024

Part 2: Building Apps More Efficiently and Following Best Practices with Copilot

Welcome to part 2 of 4 of our special blog series where we share details on our interview with Ryan Cunningham, the Vice President of Power Apps at Microsoft. We had the privilege of talking with Ryan during Microsoft Ignite in November 2023. During our conversation, we touched on a variety of topics around Power Apps and Copilot, and this series will break down the insights and announcements that were made at Ignite around Power Apps.

What does the series include?

  • Part 1: Evolution and Impact of Power Apps and AI Integration
  • Part 2: Building Apps More Efficiently and Following Best Practices with Copilot
  • Part 3: Enhancing User Experience with Power Apps
  • Part 4: Decision-Making and Learning in the AI-Enhanced Development Landscape

Part 2: Building Apps More Efficiently and Following Best Practices with Copilot

In this post:

  • Copilot is making Power Apps more accessible for citizen developers by making app development more efficient
  • Copilot is guiding users toward best practices within the Power Platform
  • Citizen developers don’t necessarily need to understand underlying code when using low-code platforms, or Copilot, to build applications

How will Copilot integration into Power Platform, especially with the capability to build tables and model-driven apps, impact the efficiency and accessibility of app development?

Ryan: Copilot integration is already significantly enhancing the efficiency and accessibility of app development within the Power Platform. By enabling users to quickly create tables in Dataverse and subsequently generate model-driven apps, we’re simplifying what was previously a complex process. This integration not only accelerates the development cycle but also makes app creation more accessible to a broader audience, reducing the learning curve. With Copilot’s assistance, users can focus more on the functionality and less on the tedious aspects of app design, making the development process both faster and more intuitive.

How do Copilot and Power Platform ensure users start their app development projects following best practices, especially regarding data management and app design?

Ryan: Copilot and Power Platform guide users towards best practices by defaulting to robust and scalable solutions like Dataverse for data management. This approach not only simplifies the development process by reducing the need for deep technical database knowledge but also ensures that apps are built on a solid, secure, and scalable foundation. By integrating best practices directly into the user experience and leveraging modern, responsive templates, the platform removes decision points that might lead to less optimal outcomes, ensuring users start their projects on the right foot.

Is it essential for citizen developers to understand the underlying code, like PowerFX, when using tools like Copilot to build apps?

Ryan: Not necessarily. The philosophy behind low-code platforms and tools like Copilot is to elevate users beyond the need to deeply understand or manage lower-level coding details. This abstraction enables greater efficiency and innovation by allowing users to focus on solving business problems rather than coding complexities. However, a basic understanding of the underlying principles can enhance a user’s ability to leverage these tools effectively and creatively. Copilot can also serve as a learning tool, helping users to gradually understand PowerFX by example.

Part 1: Evolution & Impact of Power Apps and AI Integration

Welcome to part 1 of 4 of our special blog series where we share details on our interview with Ryan Cunningham, the Vice President of Power Apps at Microsoft. We had the privilege of talking with Ryan during Microsoft Ignite in November 2023. During our conversation, we touched on a variety of topics around Power Apps and Copilot, and this series will break down the insights and announcements that were made at Ignite around Power Apps.

What does the series include?

  • Part 1: Evolution and Impact of Power Apps and AI Integration
  • Part 2: Building Apps More Efficiently and Following Best Practices with Copilot
  • Part 3: Enhancing User Experience with Power Apps
  • Part 4: Decision-Making and Learning in the AI-Enhanced Development Landscape

Part 1: Evolution and Impact of Power Apps and AI Integration

In this post:

  • Community has shaped the development of Power Apps
  • Copilot Studio is shaping technology transformation within organizations
  • The importance of governance with Copilot and how Microsoft is ensuring appropriate security of businesses’ data
  • Microsoft is on a continuous journey to ensure the output of Copilot prompts are high-quality to reduce misinformation
  • AI is democratizing development for functional and technical people, making application development more accessible

With Power Apps having evolved so significantly since its early days, could you share a key lesson or insight you’ve gained from this journey?

Ryan: Absolutely, one of the biggest lessons we’ve learned is the importance of listening to our community. It’s not just about creating powerful tools but also about understanding the real-world problems our users are facing. This journey has been about connecting technology with those who need it most, in ways that genuinely add value to their work. Seeing over 20 million users engage with Power Apps recently just underscores the impact of that focus. It’s been an incredible journey of growth and learning.

How do you envision these announcements, especially Copilot Studio and the expanded governance, transforming the way organizations approach software development and management?

Ryan: These innovations are game-changers. By integrating Copilot Studio, we’re making it easier for anyone to build sophisticated, AI-powered applications without deep coding expertise. This democratizes app development, opening up new possibilities for innovation across all levels of an organization. And with the advancements in governance, we’re ensuring that this wave of democratization doesn’t compromise security or manageability. It’s about empowering organizations to rapidly adapt and innovate while maintaining control and compliance. It’s a balance of freedom and framework that truly transforms how software serves business needs.

How does Microsoft ensure the Copilot integrations adhere to complex enterprise security models, especially when handling sensitive business data?

Ryan: Microsoft takes enterprise security very seriously, especially in the AI era. Copilot integrations are designed with the enterprise’s complex security models in mind. This means that access controls, such as role-based access and conditional access, are strictly enforced, ensuring that users can only interact with data they’re authorized to access. Our advantage lies in our deep understanding of these security requirements, from role-based access control to data sovereignty, making our AI experiences not only innovative but also trustworthy and compliant at an enterprise level. It’s about enabling businesses to confidently leverage AI, knowing their data is secure.

With the rapid advancements in AI and its integration into tools like Copilot, how does Microsoft ensure the quality of the code generated, especially considering the varied best practices in software development?

Ryan: Microsoft sets high-quality standards for the code generated by Copilot, preferring to err on the side of caution. If Copilot isn’t confident in its output, it opts not to provide potentially misleading advice. This careful approach underscores the importance of human oversight in the development process. Users are encouraged to exercise judgment and provide feedback, enhancing the system’s accuracy and reliability over time. This collaboration between AI and human insight aims to maintain high standards of quality and adherence to best practices in software development.

How does integrating AI into development tools like Copilot change the landscape for both technical and non-technical users?

Ryan: AI integration into development tools democratizes technology creation by making it accessible to a broader audience. This shift encourages a focus on the valuable expertise individuals bring from their respective fields, rather than on their technical coding skills alone. Copilot acts as a collaborative partner, enhancing users’ capabilities by providing coding assistance, thereby expanding the potential for innovation across all sectors. It’s about augmenting the human workforce with virtual technology experts, making sophisticated development more intuitive and aligned with natural language understanding.

Unleashing End User Potential: Effective Training Unveiled

Training plays a crucial role in the successful implementation and adoption of new systems or processes within an organization. However, it is important to recognize that training and testing are not the same thing. In this blog post, we will delve into the distinction between training and testing, highlighting why effective training is essential for empowering end users.

When discussing the differentiation between User Acceptance Testing (UAT) and training, it becomes evident that these activities serve distinct purposes. UAT primarily focuses on testing the system, ensuring its functionality and identifying any potential issues. On the other hand, training aims to educate end users on how to effectively use the system, tailored to their specific roles and responsibilities.

One of the fundamental differences between testing and training lies in the target audience. UAT typically involves a small subset of individuals who are directly involved in the testing process. In contrast, training aims to reach the entire group of end users, providing them with organized and comprehensive knowledge of the system. It is essential to ensure that training occurs after the system has been thoroughly tested and errors have been rectified. This prevents end users from perceiving the system as flawed, which can hinder their adoption and enthusiasm for utilizing the new solution.

Furthermore, training caters to the diverse needs and requirements of different user groups within an organization. Employees in various roles and positions may interact with the system differently, emphasizing the importance of tailoring training content accordingly. Effective training should address the unique challenges and workflows of each group, enabling end users to acquire the necessary skills and knowledge to perform their tasks efficiently.

Attempting to combine testing and training into a single activity can be counterproductive. It may lead to confusion, frustration, and a lack of clarity for end users. By keeping testing and training separate, organizations can optimize the effectiveness of each process. Testing identifies and resolves issues, ensuring a stable and functional system, while training equips end users with the expertise required to leverage the system effectively.

In conclusion, training and testing are distinct activities with separate objectives and target audiences. By recognizing the differences between these two processes, organizations can enhance the effectiveness of their training programs and empower end users to embrace new systems confidently. Tailoring training content to specific roles, conducting training after thorough testing, and ensuring clear communication with the intended audience are essential steps toward successful training implementation. Embracing these principles will enable organizations to maximize end user satisfaction, system adoption, and overall business efficiency.

Check out our training topic podcast episodes to learn more!

Scroll to top