I build mobile apps that survive real users, unstable networks,
and the occasional “it only breaks on iOS” mystery.
📍 Gaza, Palestine 🇵🇸
$ whoami
Ibrahim Deeb
$ role
Flutter-first Mobile Engineer
$ currently
Building production apps, fixing platform-specific chaos,
and pretending "just one small change" is actually small.
$ location
Gaza, Palestine 🇵🇸Cross-platform mobile apps with Flutter - from polished interfaces to real-time workflows, offline storage, payments, maps, notifications, and native platform integrations.
My work usually involves:
- Turning Figma designs into responsive, production-ready interfaces.
- Building scalable features without creating a folder labyrinth.
- Connecting REST APIs and WebSockets that occasionally enjoy surprises.
- Designing offline-first flows for unreliable network conditions.
- Integrating maps, payments, subscriptions, deep links, and notifications.
- Debugging Android and iOS issues beyond the Flutter layer.
- Refactoring legacy code before it becomes emotionally attached to the project.
Clean code is great.
Code that ships, scales, and stays understandable is even better.
Flutter · Dart · Clean Architecture · MVVM · Repository Pattern
BLoC · Cubit · Riverpod · Provider
Dio · REST APIs · WebSockets · Hive · SQLite · SharedPreferences
Firebase · FCM · Google Maps · RevenueCat · Payments · Deep Links
Git · GitHub Actions · Codemagic · JIRA · Postman · Figma
Flutter is my main playground, but I am comfortable stepping into the native layers when the app requires it.
- Kotlin fundamentals and native Android project structure.
- Android SDK, manifests, permissions, and build configuration.
- Gradle setup, product flavors, signing, and release builds.
- Platform Channels between Flutter and Android.
- Debugging Android-specific plugin and lifecycle issues.
- Xcode project configuration and build settings.
- CocoaPods, certificates, signing, and provisioning profiles.
- App capabilities, permissions, and deployment configuration.
- Platform Channels between Flutter and iOS.
- Debugging simulator, archive, and App Store build issues.
Flutter-first does not mean Flutter-only.
building:
- Production Flutter applications
- Offline-first business workflows
- Maintainable mobile architectures
exploring:
- Better synchronization strategies
- Native Android integrations
- Flutter performance optimization
- Smoother animations and micro-interactions
avoiding:
- Unnecessary rebuilds
- 900-line widgets
- The phrase "just a small change"Make it work.
Make it clear.
Make it stable.
Then find out why it only breaks on one specific iPhone.
I like clean architecture, but I do not believe every small feature needs seventeen layers, twelve interfaces, and an existential crisis.
Readable code. Stable apps. Smooth experiences. Fewer surprises.


