# App.OnStart (Depricated) It appears that Microsoft is indeed moving away from using App.OnStart in canvas Power Apps. Here are the key points: 1. Microsoft is deprecating the App.OnStart property in canvas Power Apps. This means that it's no longer recommended for use and may be removed in future updates. 2. The main reason for this change is to improve performance. Using App.OnStart can cause performance issues when loading a Canvas App. 3. Microsoft has been trying to steer developers away from using App.OnStart for several years. 4. Some specific changes and restrictions: - The Navigate function can no longer be used within App.OnStart. - Global variables and collections declared in OnStart can't be used in the StartScreen property. 5. Microsoft recommends using alternative approaches: - Use the App.StartScreen property instead of App.OnStart for navigation. - Create a dedicated "StartScreen" to load data and perform initialization tasks. 6. There is a temporary workaround: - For existing apps, you can re-enable the Navigate() action within OnStart by going to File > Settings > Upcoming features > Retired and enabling the 'Enable the Navigate function in App.Onstart' feature. - However, this is considered a temporary solution, and Microsoft ultimately wants developers to move away from using App.OnStart. 7. While Microsoft hasn't completely removed App.OnStart yet, they are actively encouraging developers to migrate away from it. 8. The full picture for alternatives is not yet complete. Microsoft is still working on providing more comprehensive solutions for scenarios currently handled by App.OnStart. In conclusion, while App.OnStart hasn't been completely removed yet, Microsoft is clearly moving in the direction of deprecating it. Developers are strongly encouraged to start migrating their apps away from using App.OnStart and adopt the recommended alternatives like App.StartScreen and dedicated loading screens.