Local first, then sync
The device database is the source of truth. Every write lands in Isar or Drift inside one transaction, then an outbox pushes it to the API when connectivity returns.
ZA Gold Flow · Fashion ERP · I.C.II’m Houssam Aziz Eldein, a Flutter engineer in Cairo. I ship production healthcare apps for Egypt’s largest children’s cancer hospital and build offline-first ERP products end-to-end — Flutter on the device, Laravel in the cloud, and a clean architecture in between.
I work on the App Development team at Children’s Cancer Hospital Egypt 57357, where the apps I ship are used by patients’ families to read lab results, track growth charts and manage appointments. Reliability isn’t a feature there; it’s the baseline.
Outside the hospital I build ERP systems end-to-end for retail businesses — gold shops and clothing stores — where the internet drops mid-sale and the cashier still has to print a receipt. That shaped how I design: local database as source of truth, a sync outbox, repositories that hide storage, and Cubits that never touch I/O directly.
I own the whole slice when needed: Flutter on phone, tablet and desktop; Laravel APIs with multi-tenant permissions and idempotent sync; Filament dashboards; store releases and over-the-air patches. I care about maintainability over cleverness — feature-first folders, typed failures, tests around the money-moving code, and docs the next engineer can actually use.
Patient-facing apps on the App Store & Google Play, with biometric locks, secure screens and OTA patching.
Isar / Drift local databases, write queues, sync outboxes and realtime invalidation across devices.
Flutter apps plus Laravel 13 / Filament backends with multi-tenant RBAC, subscriptions and sync engines.
RTL layouts, bilingual l10n and typography tuned for Arabic readers — every product I ship is bilingual.
Everything here comes from real codebases: production hospital apps, ERP products and open-source projects. No résumé padding.
Four products, ranked by real-world impact and technical depth. Click any one for the full case study — problem, architecture, my role, challenges and results.
This is the actual data flow inside ZA Gold Flow, Fashion ERP and the 57357 apps. Hover a layer to trace its connections; click it to read how it’s implemented.
The device database is the source of truth. Every write lands in Isar or Drift inside one transaction, then an outbox pushes it to the API when connectivity returns.
ZA Gold Flow · Fashion ERP · I.C.IRepositories own Dio, Isar and Firebase. Cubits orchestrate state from watch streams and typed results, so screens stay testable and swappable.
Every feature-first codebaseAPI calls return Either<Failure, T> through a single safeApiCall, so error handling is uniform and never an afterthought.
Pricing, stock deltas, instalments, receipts and sync ordering are covered by unit tests before UI polish — 70+ test files across the ERP products.
Fashion ERP · ZA Gold FlowBiometric locks, secure-mode screens, device-bound tokens in secure storage, restricted API keys and server-side permission resolution.
Ana 57357 · AttendSmartArchitecture blueprints, per-feature docs and loading-practice guidelines — so the next engineer (or future me) doesn’t reverse-engineer the codebase.
I.C.I blueprint · 16 ERP design docsMost production work lives in private hospital and client repositories. The public ones are pulled live from GitHub.
Private work: Ana 57357, 57357 Out Services, 57357 donation app (hospital Azure DevOps) · ZA Gold Flow, Fashion ERP, AttendSmart, I.C.I (client repositories).
Hiring for a Flutter role, need an offline-first product built end-to-end, or want a second opinion on your mobile architecture? I usually reply within a day.