The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Flutter 3.47 made one of my desktop performance tests faster.
The screen still janked.
That wasn’t a contradiction. I was measuring two different bottlenecks as if they were one.
Impeller now prepares engine shaders before runtime on macOS, Windows and Linux. That removes shader compilation from the middle of a frame.
But it cannot rescue a list that rebuilds 200 widgets on every scroll tick. That work happens on the UI thread before the GPU gets a chance.
The profiler separates them:
• Dark-red shader-compilation frame → renderer or shader problem
• Ordinary slow frame → inspect rebuilds, layout and CPU work
My upgrade check is now simple: record the same interaction in profile mode three times before and after Flutter 3.47, then export the timeline JSON.
If the shader spike disappears, the renderer upgrade worked. Any remaining jank is ours to investigate.
I wrote the complete desktop retest list, including the golden-test failures you should expect:
What did Flutter 3.47 improve in your desktop app—and what stayed slow?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
All Eyes on You!!👀
100 eyes. One cursor. And absolutely nowhere to hide.
Built for the Rive Halloween Challenge with RML, Luau, and WGSL shaders.
looking scary af 🔥
Flutter 3.47 made the Widget Previewer stable, and the first thing most teams will do is point it at a screen that boots the app. That one renders an error, not a component.
⚠️ 𝐖𝐡𝐲 𝐢𝐭 𝐟𝐚𝐢𝐥𝐬: the previewer runs browser-backed. Native plugins, dart:io and dart:ffi are unsupported, and changing global state needs a full restart.
I've stopped reading those errors as tooling gaps. A widget that reads an injected value previews fine, because you can put a hand-written fake above it. One that builds its own dependency cannot.
🔍 𝐓𝐡𝐫𝐞𝐞 𝐜𝐡𝐞𝐜𝐤𝐬 before you annotate anything
Does it initialize a service on the way to the first frame? Move that to the composition root.
Does the constructor require arguments? Annotate a top-level factory function instead.
Does it have an intrinsic size? If not it auto-constrains to about half the preview frame, so pass size.
✅ 𝐒𝐭𝐢𝐥𝐥 𝐧𝐨𝐭 𝐚 𝐭𝐞𝐬𝐭. A preview asserts nothing and never runs in CI. Keep the golden test for the dependency bump that shifts your card padding at 03:00.
Six failure modes, and the conventions that survive a design system. https://www.duskolicanin.com/blog/flutter-widget-previews-3-47-guide
PULSE — Project Management SaaS Dashboard
PULSE is a modern Project Management SaaS dashboard designed to help teams manage projects, tasks, deadlines, and collaboration from one workspace.
The interface focuses on clean information architecture, clear hierarchy, structured tables, and efficient team workflows.
Total 6 Screens
• Dashboard
• Projects
• Project Details
• Tasks
• Team
• Calendar
Focus: SaaS UI/UX • Dashboard Design • Project Management • Tables • Team Collaboration • Responsive Web UI
Six screens with a clear structure, nice. Structured tables are where PM tools usually fall apart once real data hits them (long names, 200+ rows, empty states), and your layout leaves room for that. As a developer who builds dashboards like this, I'd love to see how the...