“ improved app rendering “ is actually not improved!!!

[Qlxr332]

I tried several times to change my app to rendering mode, it gives user very bad experience!

The most important is ,under rendering mode, the app runs slow like hell! While classic mode is far more efficient than rendering mode!

Please don’t take classic mode away!

The app speed is the most important factor compare to some other fancy new function that rendering mode could bring us!

In between fast app and fancy functions app, I would definitely choose the first one , why not keep improving classic mode?

[dinusc]

Hello @Qlxr332,

Thank you for your feedback.

I would like to assure you that the "classic rendering" mode will not be taking away until all the issues are resolved. We're constantly working on all the issues related to the "improved rendering" mode. With that being said, it would very helpfull for us to get more information about the issues you experience. A test application or the detailed steps on how to reproduce those problems would be very much appreciated.

[Qlxr332]

I do notice the bugs has been constantly fixed, thanks for that,
But the big concern is the speed, if turn on the rendering mode, it obviously slowdown the app, the loading speed, click button navigation speed, scrolling speed etc, it feels an old man! It is not microsecond, it is noticeable speed gap between two mode.

[dinusc]

Is this related to a specific application, specific functionality or specific control? What would be your recommendation for building a test application to reproduce the problem (certain controls, complex filtering, large data volume, many sources or else)?

Thank you.

[miglisic · Accepted solution]

At the end of last week, we released a number of fixes to improved rendering issues. Please try re-publishing your apps with improved rendering and let us know what, if any, issues you still face.

We continue to focus on resolving these problems. Really appreciate everyone's help and patience with this!

[Qlxr]

Thanks for attention and continued effort on improving rendering model.

I tested with my app , it is better now , but still could not catch up with classic model’s reaction speed, what I mean reaction speed is screen transaction time , when the screen has large on visable action, it take at least twice time compare to classic model.

To me ,APP speed is the key, so I will still stay in classic model until rendering model can be more efficient on rendering.

[hjaf]

@miglisic 
Good to hear that the improved rendering is still considered as a work in progress and that you are still working on fixes.

However, the warning in studio saying that improved rendering will be enforced at some point is very worrying. It is currently not possible to do testing (in production) on the improved rendering because the apps crash (restarts without any error) more or less all the time. "standard" rendering seems to be working just fine.

In short, improved rendering is basically unusable for our teams at this point, and it would be quite serious for us if these issues is not improved by the time developers decide to enforce it.  

Can you say anything about when and what conditions must be in place before the enforcement will take place? And if there is any way to retain the standard rendering if the issue is not resolved when the enforcement takes place?

We are currently running iOS 12.2 and currently using powerapps version 3.19053.21. 
(Standard browsers does not seem to have an issue with the Improved rendering.)

Edit:

Response to the issue can be found here