Putting it all together

1. Putting it all together

You've got a multi-screen app: gallery, detail screen, edit form, validation. This video is the integration lap. You'll ship the app end-to-end, then check it like a pro using the App checker before declaring it done.

2. What you've built so far

A quick lap of what you have. The Browse screen shows your tickets, filterable by status and searchable by title. Tap any row and Set(selectedTicket, ThisItem); Navigate(DetailScreen) carries that ticket to a detail view. From the detail screen, an Edit button takes the user to a form, where IsBlank + DisplayMode block bad submits and SubmitForm writes back to your data source. That's a real working multi-screen canvas app. Now we make sure it stays working.

3. The App checker

The App Checker is Power Apps' built-in linter. It lives in the top-right of Studio, a small icon shaped like a stethoscope. Open it and Power Apps scans every formula, every property, every screen, and groups what it finds into categories. The two you'll work with in this course are Formulas, for broken references and delegation problems, and Accessibility, for missing labels and poor contrast. Run it before every publish.

4. Formulas tab

On the Formulas tab, you see three severity levels. Red errors are formulas that genuinely don't work, reference to a deleted control, a property typo, a missing data source. Fix these immediately or your app breaks at runtime. Yellow warnings flag delegation problems and other performance pitfalls. You met this one in Chapter 2's filter video. Blue info entries are stylistic, unused variables, dead-code branches. Worth cleaning, not urgent. Click any entry and Studio jumps to the offending formula.

5. Accessibility tab

The Accessibility tab is the one most beginners ignore and most users notice. Screen readers need an AccessibleLabel property on every input so they can announce what the field is for. Body text needs enough contrast against its background, light gray on white reads cleanly to sighted users, terribly to anyone with low vision. And the tab order should match the visual order, if Tab jumps from the Title input straight to the Save button, skipping Priority, the keyboard user is stuck. Fix accessibility findings the same way you'd fix red errors.

6. Fixing a finding

Fixing a finding has a predictable shape. Click the entry, Studio navigates to the screen and selects the offending control. The property at fault is highlighted in the right pane. You make the edit in the formula bar, set the AccessibleLabel to a descriptive string, increase the Color contrast, rewire a broken reference. Then re-run App Checker by clicking the refresh icon at the top of the panel. The fixed finding disappears. The remaining count drops by one. Repeat until the panel is clear.

7. What you'll build

The exercises pull everything together. You'll walk the app end-to-end, add the final edit wire-up, and use App Checker to clear any warnings before shipping.

8. Let's practice!

Time to ship your app end-to-end, then check it like a pro.

Create Your Free Account

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