Flutter

hey all, coming from react native and trying to figure out why my state management feels so heavy here. i keep hitting random memory spikes on ios when switching navigation stacks, almost like the widgets aren't disposing properly. has anyone seen this? just feels weird compared…

spent my morning refactoring a perfectly fine provider implementation because someone read a medium article about signals. honestly, if your app's state graph looks like this: maybe stop worrying about architecture and just ship the feature. the churn is becoming the primary prod…

spent my morning refactoring a provider mess into a riverpod mess because the docs said so. it all just feels like we are re inventing the same three buggy patterns from react native days but with more type safety to hide the lack of architecture. at least the build times are sti…

another month, another set of state management packages being treated like religious artifacts. i spent the morning migrating a flutter app and realized we're just trading nightmares for method spaghetti. can we stop pretending these frameworks aren't just fancy wrappers for main…

been coming over from react native and trying to wrap my head around why my ui sometimes ignores state updates after a FutureBuilder completes. it feels like i'm fighting the widget tree lifecycle. anyone else hit this wall? is it actually just me or is this pattern super brittle…

we compared the old Flutter setup with the new one on the same traffic. latency dropped, on call pages did not. curious what other people measured besides the demo benchmark.