I'm hoping there's some kind of planned performance improvement work on the gallery control, but posting this, in case there isn't.
At present, the gallery control is incredibly clunky/laggy when scrolling any faster than what I'd consider to be "unreasonablly slow". The behavior is
I will note:
I'm attaching a video of this behavior. While the lag you see might be "acceptable", it's not a great user experience on any platform. I understand that the gallery is probably working as designed for keeping resource utilization low on mobile devices, however, since this can be reproduce on mobile, too, I'm asking that Microsoft improve this.
I have the same problem.
At the time of screen transition, all data displayed in the gallery is loaded into the local collection. However, there is a lag of about 5 seconds when scrolling through the gallery.
In my case, the scrolling time is very long, probably due to the use of nested galleries.
Gallery scroll "blank time" of several seconds happens even with a plain gallery (not nested). Performance gets REALLY poor when you have nested gallery with several hundred items in it, numerous columns and fields. Completely unusable in a desktop app for displaying large amounts of data.
I really don't understand how it's possible that more people aren't bothered by this, it makes for such a poor showing when you actually make something useful and people keep asking you why is the scrolling so bad.
The user experience is just abysmal, people are so used to snappy things with android and apple apps, so anytime they see something that kinda "lags" they just dismiss it on the spot.
I'm also pretty shocked at how bad this performance issue is. I am building a PowerApp to replace an existing slow app built elsewhere years ago. I will never get buy in from the users if performance is actually worse when doing something as simple as scrolling a small number of records.
Come on Microsoft!!
This gallery performance really is a nightmare.
Accidental double post that I can't figure out how to delete.
Is there still no solution/workaround a year later?
User | Count |
---|---|
212 | |
94 | |
85 | |
49 | |
38 |
User | Count |
---|---|
271 | |
103 | |
103 | |
60 | |
59 |