FEATURED WORK

Four projects, one developer.

These are the four I keep coming back to. Each one is a real internal tool used daily. The apps themselves are private, so this page is where their stories live.

01 · WhatsApp Platform 02 · HR & Payroll 03 · iOS App 04 · Ops Portal
● Live 2025 · Full-stack SaaS

Support platform on WhatsApp

A shared inbox, smart conversation routing, agent permissions, campaigns, and five live reporting views — built to replace a paid third-party WhatsApp tool with something the team owns.

Operations dashboard

The problem

The team was paying for a third-party WhatsApp tool with hard limits I kept hitting — agent count, campaign volume, reporting depth. Every workaround was another spreadsheet.

What I built

  • Shared inbox that assigns each chat to one available agent — never two at once
  • Agent permissions matrix — every capability flows through one Terms & Roles table
  • Five live reporting views: SLA, agent performance, response time, backlog, campaigns
  • Campaign manager with database-driven message templates
  • Notifications three ways: sound, on-screen alert, and browser notification

The interesting bit

The permission system is one matrix. Every button, every filter, every route checks the same source of truth. Adding a new role is one row, not a hunt through the codebase.

Open the full case study →

● Live 2024–2025 · HR & Payroll

HR system with Egyptian payroll

A full HR platform built for a client still on spreadsheets. Twenty-six tables, a payroll system that handles Egyptian tax and social insurance correctly, plus a mobile app so people can check in from wherever they actually are.

HRIS dashboard preview

The problem

A client with 200+ employees was running everything on spreadsheets — attendance, leave, and payroll. Every month-end was a days of checking numbers by hand, and Egyptian tax law made it worse.

What I built

  • 26-table Postgres schema covering employees, contracts, attendance, leave, payroll
  • Tax and social-insurance calculations that match how Egyptian law works in practice
  • GPS-based attendance in a mobile PWA — check in from the actual work site
  • Leave request workflow with approval chains
  • Full admin dashboard with month-close and payroll runs

The interesting bit

The payroll engine was the hardest part — not the math, the edge cases. Prorated first months, mid-cycle raises, unpaid leave, insurance ceiling changes. The rules aren't written in one place — I collected them from real HR work.

Open the full case study →

● Live on App Store 2024–2026 · iOS & PWA

Studio booking iOS app

A yoga studio was running bookings on WhatsApp. I built them a booking app for iOS — from first line of code to App Store release, without owning a Mac. The whole toolchain runs in the browser and in cloud CI.

Align with Enjy iOS app

The problem

Every Sunday night the studio owner was retyping the class schedule into a WhatsApp broadcast. Bookings arrived by DM. Cancellations were remembered, not tracked. Payments were on a spreadsheet.

What I built

  • Class schedule with drag-to-reorder and "Copy last week" so nobody retypes at midnight
  • Booking flow with class-credit balance, waitlists, and cancellation windows
  • Push notifications through APNs for class reminders and studio announcements
  • Native iOS shell over the PWA using Capacitor, built in the cloud via Codemagic

The interesting bit

Shipping to the App Store without a Mac took time to get right — Codemagic runs the iOS build, code-signing happens on their machines, TestFlight submissions go through Fastlane. I write the code in the browser, push, and 20 minutes later there's a new build in TestFlight.

Open the full case study →

● Live 2024–2025 · Workforce & operations

Operations & workforce portal

Three apps that work together for the team running daily operations — an admin panel, an agent dashboard, and a campaign runner. Vanilla JS, Supabase, and a lot of realtime.

Admin panel

The problem

The operations team was juggling three different tools for scheduling, agent break tracking, and outbound campaigns. Data lived in disconnected places. Managers spent hours reconciling.

What I built

  • Admin panel: workforce scheduling, break compliance, KPI dashboards, real-time roster
  • Agent portal: shift schedule, break requests, KPI view, notifications
  • Campaign portal: outbound campaign runner with database-driven call scripts, duplicate handling, live agent notifications
  • Shared Supabase backend so all three apps read from the same tables

The interesting bit

I kept it plain JavaScript on purpose — no framework, no build step. It loads instantly, and I can fix any problem right in the browser. Sometimes the simple choice is the right one.

Open the full case study →

Want to see what I can build for your team?

Fastest reply is WhatsApp — same day, in Arabic or English.

WhatsApp me