The docs seem to imply that HybridComposition is a newer technique, and it was created in response to problems of dynamically interacting with the underlying UI. As a cost, one of the above links warns us:
While a platform view is rendered with Hybrid Composition, the Flutter UI is composed from the platform thread, which competes with other tasks like handling OS or plugin messages, etc.
I think this caused video to be unwatchable on cheaper Amazon Fire Kindles for me. (I have a rive animation playing as well, so that might be the straw that broke the camel's back). So I just opted in to the older Virtual Display mode, which for me is OK since I don't need to send touch events to the underlying web view.
So, has anyone else found choosing one of these modes has performance impact?
I just wanted to post my findings here and see if the community had anything to add. Sorry I could not find a message board or some other venue.
YoutubePlayerFlags has a flag called useHybridComposition which is on by default.
Evidently the mode of rendering native UI is a complex topic with a lot of opinions: https://github.com/flutter/flutter/wiki/Android-Platform-Views https://github.com/flutter/flutter/wiki/Hybrid-Composition#performance
The docs seem to imply that HybridComposition is a newer technique, and it was created in response to problems of dynamically interacting with the underlying UI. As a cost, one of the above links warns us:
While a platform view is rendered with Hybrid Composition, the Flutter UI is composed from the platform thread, which competes with other tasks like handling OS or plugin messages, etc.
I think this caused video to be unwatchable on cheaper Amazon Fire Kindles for me. (I have a rive animation playing as well, so that might be the straw that broke the camel's back). So I just opted in to the older Virtual Display mode, which for me is OK since I don't need to send touch events to the underlying web view.
So, has anyone else found choosing one of these modes has performance impact?