Power Apps gives us a property called the App On Start which allows us to put in formulas which will run when our apps are initially launched. There are several use cases which we might use the App On Start in Power Apps like caching data to use throughout our apps and a technique called deep linking which involves passing parameters into Power Apps with the Param() function and most commonly using the Navigate function to route to a particular screen depending on the parameter that is passed.

But there’s a problem with the On Start in Power Apps and specifically with using the Navigate function in the On Start, it’s imperative and it really can kill your performance. In this video, I outline a brand new property that Microsoft just released for Power Apps called the App Start Screen. This gives us a declarative way to programmatically tell Power Apps which screen we want to show at the start of our app.

I’m going to break down all of the details of this new property and what you need to do to start using it in your Power Apps.

🔗 Power Apps Start Screen Announcement: https://powerapps.microsoft.com/en-us/blog/app-startscreen-a-new-declarative-alternative-to-navigate-in-app-onstart/

💠 Power Apps Deep Linking: https://youtu.be/EZyxlYtzqTQ
💠 Power Apps Performance Tips: https://youtu.be/UuIwB8YYKao

Table of Contents:

00:00 – Intro
00:41 – What's Changing?
01:25 – The Problem with App.OnStart
03:40 – What’s Changing with OnStart Property?
04:22 – Find your Power Apps Editor Version
04:45 – Using the New Start Screen Property
08:55 – Configure OnStart Retired Feature

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.