What's next

1. What's next

Your app is built and shipped. This video is the forward look, a quick tour of the wider Power Apps ecosystem and where to go next.

2. When Dataverse beats SharePoint

A single SharePoint list works well for one team. But when your app needs records linked across multiple tables, like tickets tied to users tied to departments, that's where Dataverse shines. Dataverse gives you proper relationships between tables, role-based security so different users see different data, scale into hundreds of thousands of records, and a place for business logic that travels with the data instead of living inside each app. Pick Dataverse when relationships, security, scale, or business logic matter.

3. Copilot in Power Apps

Power Apps Studio now ships Copilot inside the maker experience. Ask it to add a button that emails the assignee, explain an existing formula, or suggest a fix when App Checker flags an error. Treat its output as a starting point, not a finished answer. The formulas you've learned this course are still what you'll read, debug, and review; Copilot just drafts them faster. This course teaches stable Power Fx fundamentals you can rely on in every tenant. Copilot is there when you have an apps backlog.

4. Model-driven apps in 60 seconds

Quick reminder from Chapter 1. Model-driven apps are the second flavor of Power Apps. Instead of designing every pixel, Power Apps generates the screens for you from your Dataverse tables. Same data, different building style. Model-driven shines for CRM, case management, anywhere users navigate many related records with consistent layouts. Harder to make pretty, easier to scale.

5. Solutions and ALM

Two intermediate concepts. A Solution packages the moving parts of your app, the screens and controls, the tables and data model, flows, connection references, and related configuration, into one transportable bundle. The business records themselves aren't usually part of it; those live in the destination environment. You build in a Dev environment, export the Solution, import it to Test, then to Production. That's application lifecycle management for Power Apps. The default environment is fine for prototyping, but production apps live in their own environment with their own Solutions. It's worth knowing about as your apps grow toward production.

6. AI Builder

Two AI features to know about. AI Builder is a set of pre-built models you drop into a canvas app to extract data from receipts, parse a form, or judge sentiment. You don't train the models; Microsoft ships them ready to use. Copilot, which you saw earlier in Studio, is different: it helps you as a maker by generating controls from natural-language prompts and explaining existing formulas. Think of AI Builder as AI for your app's users, processing their documents and data, and Copilot as AI for you, the app builder, speeding up development. AI Builder requires premium licensing, which is why we don't use it in this course.

7. Accessibility basics

A real Power App that ships to a school district reaches users who can't see the screen clearly, can't use a mouse, or rely on keyboard navigation. Three levers cover most of the gap. AccessibleLabel on every input gives screen readers something to announce. Text color and background need enough contrast to read at arm's length. The tab order, which you set with the TabIndex property, should match the visual order. You'll reason through these in the exercises.

8. Let's practice!

Let's check what you've learned about the wider Power Apps ecosystem.

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.