Reading <this article> about Flutter 3.3, I can’t ...
# compose
a
Reading this article about Flutter 3.3, I can’t help but wonder if Impeller is coming to Compose 🤔
a
But Impeller is something similar to Filament right?
If it is Filament could work on Compose as well, right?
a
I will admit, I don’t know much about Filament except that Romain Guy makes cool-looking 3D renders in it. Impeller seems to be solving many of the problems that cause jank that we see with Compose rendering.
a
Filament does work in compose, and I'm writing an applier for a work project. Still very rough unfortunately
Filament can be used via View interop, but at a high level something like impeller would end up probably becoming the host view, and replace any draw context operations with impeller methods, behind a JNI
Not sure if there'd be much benefit, Android already uses SKIA nowadays and I'm certain it would be much more efficient as is, and I'm sure performs any shader caching AOT as everything is drawn using it excluding surfaces I would think
a
But Flutter also used Skia and now they’ve developed this to overcome the performance issues. Maybe they don’t have baseline profiles like we do though?
a
SKIA is embedded in the flutter engine, and loaded at runtime
There would be another SKIA lib running alongside the system
a
Wait, you mean Android itself uses Skia nowadays for rendering? That’s interesting. I wasn’t aware of that.
a
Yeah, iirc, they used it initially, switched to a different rendering backend, and switched to it again
Android 13's AGSL is pretty much SkSL, verbatim afaik
All SKIA