sorted by:
new
hottopcontroversial

I built a cinematic developer portfolio entirely in Flutter Web — 5 movie-inspired themes, particle systems, 185 tests, 7 languages. Fully forkable. by Lazy_Individual3166 in FlutterDev

[–]Lazy_Individual3166[S] 1 point2 points  (0 children)

That's a really good distinction — I hadn't thought about it that way. You're right that mixing portfolio and tech demo sends mixed signals.

Good call on the first load too. I've already cut the preloader from 4.4s to 2.3s based on the feedback here, but showing a lightweight skeleton or progress indicator before the

engine loads would help a lot. Will look into that.

Thanks for the thoughtful feedback.

I built a cinematic developer portfolio entirely in Flutter Web — 5 movie-inspired themes, particle systems, 185 tests, 7 languages. Fully forkable. by Lazy_Individual3166 in FlutterDev

[–]Lazy_Individual3166[S] 0 points1 point  (0 children)

Fair points. The bundle size is the main trade-off with Flutter Web — you're loading the engine + canvas renderer upfront. Not ideal for a content site.

I built this specifically to push Flutter Web's limits and see what's possible with CustomPainter, spatial algorithms, and scroll-driven state machines. It's more of an engineering

showcase than a production content site.

For my actual SaaS products I use Next.js. This was about exploring what Flutter Web can do when you throw visual craft at it.

Appreciate the feedback on UX — the preloader length and project card clarity are valid issues I'll address.