Introduction to performance optimization
Optimizing an app's performance is as important as making an app that works. In today's world, its all about things being fast. User adoption reduces significantly or even drops to zero if an app isn't performant. The concept of democratization makes business users and technical IT resources can both build Power Apps. While this is great, the problem is that there are different ways to implement or build an app. Not saying that one set of makers will always be better than the other, but this highlights the importance of paying special consideration to making an app as fast as possible.
Examples of optimizations in Power Apps
Over the past few days, I have written a few blog posts on specific examples showcasing opportunities where you can easily make an app more performant without breaking any functionality. I want to use this place as a shell for all those other posts so you can find them easily in one place. The 1st 9 posts are about how to optimize:
- Lookup function by not using dot operator
- Fetching multiple columns of a record
- Passing a record to Patch
- Fetching multiple records from a table
- Concurrent multiple unrelated data calls
- Data calls inside a gallery
- Cross screen dependencies
- Performance by trashing extra screens and controls
- Fetching the same value again and again
- How to use the Power Apps monitor tool
To learn more about performance in Power Apps, you can read the official documentation here.