Flutter 3.47 shipped in August 2026 and closes out a multi-year architectural transition: Impeller, Google’s purpose-built rendering engine, is now the default renderer on Windows and enabled by default on Linux, joining iOS, Android and macOS where it was already standard. The practical win is that Impeller compiles a fixed set of shaders at build time instead of compiling them on the fly the first time an animation runs — which is what causes the brief stutter, known as shader compilation jank, that’s dogged Flutter apps’ first-run performance since the framework launched. Google’s release notes are explicit that the old Skia-based renderer is on borrowed time: fallback options still exist on desktop platforms for now, but the company says they’ll be removed in a future release and is asking teams still relying on Skia to file bugs rather than assume long-term support.
For anyone commissioning a Flutter build, this closes a gap that’s been a legitimate reason to hesitate on the framework for polish-sensitive apps: inconsistent first-run animation smoothness, particularly on lower-end Android devices. That’s no longer an open question — it’s now a solved, shipped default across every platform Flutter targets, which strengthens the case for treating Flutter as a genuine first choice for cross-platform builds rather than a budget compromise against native.
So what
If you’re scoping a new cross-platform app or evaluating whether an older Flutter codebase needs a performance pass, this is worth checking against directly — an app still pinned to Skia via a legacy project flag is running on a renderer Google has now told you to stop relying on. See our platform & API work for cross-platform builds, or get in touch to talk through the right framework choice for your project.