> I build Flutter apps that ship to the stores and stay maintainable
  after launch. Clean Architecture, feature-first structure, state
  chosen per feature, Firebase and REST/GraphQL on the backend side.

> 5+ years of Flutter across product teams in Saudi Arabia, Morocco,
  Libya, Türkiye, the UK and Egypt. Five apps live on Google Play
  and the App Store, several built solo from empty repo to release.

> I'm known for the awkward part of mobile: apps that work with no
  signal, Arabic-first RTL by design, and payments across seven
  gateways.

> The hard part is never the first screen. It's the codebase still
  being easy to change a year later.

Apps in production, built and published end to end.

Published apps

• MisMar — Arabic-first vehicle maintenance and repair platform for Egyptian drivers, with a seven-stage service flow from request to delivery. Current role.
• Arcit-AI — social platform matching architecture and home-improvement providers with clients, with AI-driven matchmaking. App Store · Google Play
• Lpermis / Lpermis Pro — driving-theory testing and lesson booking for driving schools across Morocco, plus a multi-role edition for schools. Led from architecture to release. Lpermis (Play) · Lpermis Pro (Play)
• Mutabbib — medical social network connecting patients with hospitals, clinics and doctors; real-time scheduling lifted bookings 25%. App Store · Google Play
• Saber Yamen — multi-vendor marketplace for new and used items, built from scratch. App Store · Google Play

_{Also shipped: Dental Dinar · FreeDoc · O'Permis · Savior App}

Client work

• AYCO Maintenance Reports — Arabic-first field-service app for medical-equipment maintenance: barcode scanning, on-device signatures, and QR-coded PDF reports. Built solo on Flutter and Firebase.

  How it works offline

  • Firestore writes race a timeout; if the timeout wins, the technician sees queued, not failed, and the visit syncs later.
  • Up to 100 devices per visit, written in resumable 25-report transaction chunks, with report numbers issued transactionally.
  • Three-role permissions (super admin, admin, technician) enforced server-side in Cloud Functions and security rules.
  • Two build flavours bound to separate dev and prod Firebase projects.

• Delivery platform — subscription-based access with timed visibility of incoming requests.

• Sports platform — Flutter client integrated with an existing GraphQL backend.

How I build

• Clean Architecture, feature-first — each feature owns its data, domain, and presentation layers.
• State chosen per feature — Riverpod, Bloc / Cubit, Provider or GetX, matched to the complexity and data flow.
• Firebase + REST / GraphQL for auth, data, and push — with offline-first sync and server-side authorisation.
• Architecture before code — the plan comes first, generation and implementation second.

Mobile

Backend & Data

Tooling

_{Also shipped with: Cloud Functions · Firestore Security Rules · Hive · Pusher · Google ML Kit · Google Maps · Provider · GitFlow · unit & widget testing · payments via FlutterWave, PayU, PayPal, PayStack, Moyasar, Fawry, Stripe}

Speak a transaction in Arabic, get a structured entry.

▸

Five chapters that unlock in order, progress saved to Postgres, and answers kept server-side behind row-level security so the quiz can't be beaten from the network tab. React, Vite, Supabase.

▸ js-basics-quiz.vercel.app

📧 [email protected] · 🔗 linkedin.com/in/mormdn · 🌐 mormdn.com

_{B.Sc. Computer Science — Bioinformatics, Mansoura University (2021) · 🇪🇬 Arabic native · 🇬🇧 English professional working proficiency}