AbedDev
Software Engineer specialized in Mobile App Development, currently based in Dubai.
I craft sleek, portable digital solutions using just a smartphone and a sharp mindset.
💻 I code fluently in Dart, Kotlin, and C++/C, building apps that are both powerful and user-friendly.
📱 My mission? To create mobile-first tools that solve real problems—fast.
Перестаньте усложнять приложения Riverpod, добавляя слишком много поставщиков 🚫 | Ошибка управлен...
Ошибка №5 в Flutter Riverpod: забываем про AutoDispose ⚡ | Предотвратите утечки памяти в вашем пр...
🔥 12 изменений в мышлении руководителей мобильных инженеров в 2025 году 🚀 | Станьте разработчиком...
Ошибка Riverpod №4 — перестаньте создавать поставщики внутри виджетов ❌ | Совет Flutter Pro
19 лучших практик Flutter для приложений профессионального уровня (руководство 2025 г.)
Ошибка Riverpod №3 — наблюдение за поставщиками в неправильном месте (исправьте свои перестройки)
Riverpod Mistake #2 — Not Disposing Providers (Silent Memory Leaks)
🚀 20+ Pro Coding Practices Every Mobile Developer Should Master | Flutter & Dart Best Practices
Riverpod Mistake #1 — Returning Futures from Plain Providers (Broken Async State)
15 Pro Android Studio Tricks for Flutter & Android Developers | Code Faster, Debug Smarter 🚀
Avoid These 11 Costly BLoC Mistakes in Flutter Apps 🚫
BLoC State Management Mistake #11 — Tightly Coupled BLoCs (Here’s the Clean Fix)
BLoC State Management Mistake #10 — Hardcoding Dependencies (Kills Testability!)
BLoC State Management Mistake #9 — Uncancelled Stream Subscriptions (Memory Leaks!)
BLoC State Management Mistake #8 — Accessing Context’s Bloc Too Early
BLoC State management Mistake #7 — Nested BlocBuilders (Use BlocSelector Instead!)
BLoC State Management Mistake #6 — Navigation Inside the Bloc (Why It's a Bad Idea)
BLoC State Management Mistake #5 — Missing or Broken Equatable (Silent UI Bugs)
BLoC State Management Mistake #4 — One Giant State Class (Avoid This!)
BLoC State Management Mistake #3 — Not Closing Your Bloc (Memory Leak Warning!)
BLoC State Management Mistake #2 — Don’t Call Events in build()
BLoC State Management Mistake #1 — Putting Logic in the UI (Don’t Do This!)