Local LLMs running fully on device means user data never hits a server. No API calls, no logs, no third party agreements. For devs building sensitive apps, this isn't just a trend. It's the architecture shift we actually needed.
English
Abdulkabir Adekanye
1.6K posts
Abdulkabir Adekanye
@_KanyeDev
Flutter App Developer | CEO @CyrexTech_
Katılım Ocak 2020
84 Takip Edilen223 Takipçiler
Not every widget needs its own file, fam.
Splitting obsessively kills context. Sometimes keeping related widgets together is just cleaner code.
Read the room, not the rulebook.
English
Clean Architecture in Flutter is mid for most apps.
You're not building Google Maps. The extra layers just mean more files, more boilerplate, and slower shipping.
Sometimes the real move is knowing when NOT to over-engineer.
English
@_KanyeDev Totally. Every dev who said they’d add flavors after they were done building the app never did 😂
English
@thedevwriter Ha, the graveyard of good intentions. I've seen so many 'we'll refactor it later' promises evaporate. Starting right pays dividends fast.
English
Stop copy-pasting try-catch across every Flutter service.
A Dio interceptor catches network and HTTP errors (timeouts, 401s, 404s) in one place.
Just remember: it's your first line of defense, not the only one.
English
@larrybson21 Exactly 💯
Need to ensure everything is solid
English
@_KanyeDev Absolutely, can never be to careful when creating a Flutter app
English
@thedevwriter Exactly. Setting it up from the start saves so much friction down the line. The pain of retrofitting flavors later is real.
English
@michaelbushe Same here. Setting them up early saves so much refactoring pain down the road. Plus it forces you to think about your app structure from day one instead of bolting it on later.
English
@_KanyeDev Better not to use it at all. Especially for enterprise apps
English
Putting your Future inside FutureBuilder's build method restarts the task on every rebuild. Each build call creates a new Future object, and FutureBuilder compares by reference, so a new instance means a fresh start.
Fix: initialize it once in initState(), store it in a field
English
@Shahood Neat part: that's the one nesting case that doesn't need slivers. Horizontal-in-vertical is just nested ListViews, inner gets a fixed height. Even in a CustomScrollView it'd sit in a SliverToBoxAdapter as a plain box. Slivers earn their keep composing the same axis.
English
@_KanyeDev ...and when u have to show a horizontally scrolled list inside a vertically scrolled list.
English
SliverList shines in CustomScrollView for complex UIs. But for a simple list? ListView.builder is easier and wraps SliverList internally anyway.
Use Slivers directly when composing SliverAppBar, SliverGrid, or SliverPersistentHeader combos.
English
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
Don't use FutureBuilder.
#Flutter #Flutterdev
Abdulkabir Adekanye@_KanyeDev
Putting your Future inside FutureBuilder's build method restarts the task on every rebuild. Each build call creates a new Future object, and FutureBuilder compares by reference, so a new instance means a fresh start. Fix: initialize it once in initState(), store it in a field
English
Skipping dispose() on controllers and un-cancel()ed stream subs is how leaks hit prod. The order matters: dispose/cancel everything you own first, then super.dispose() last, never touch this after super runs. leak_tracker in tests catches the rest.
English
Using BuildContext after an async gap without a mounted check ships crashes to prod. Debug catches it; release burns users.
The fix: if (!mounted) return in State, if (!context.mounted) return elsewhere (Flutter 3.7+).
Better yet: don't pass context across async
English
@ASalvadorini @antigravity 🤣🤣 That is wild, they should do better!
This current quota won't even be enough for a Hello World lol.
English
@_KanyeDev @antigravity Yes! 😂
The first prompt takes 2m. The remaining 28m are spent trying to fix the pure 💩 the first prompt did 😅
GIF
English
Did @antigravity just restricted its quotas again? 🤐
I must have coded 3 hours today, and I consumed 25% of my weekly quotas, using Gemini 3.5 Flash (High).
This becomes totally useless if I can't even code a few hours a day 😭
#AI #gemini #Google #antigravity
English