Technical work, in detail

One calendar app, every calendar, zero forms.

A personal iOS calendar app that turns a plain sentence — “dinner with Sam friday 7pm” — into a real event written to all of your calendars at once: Apple, Google, and Outlook. The copies are tracked as a single mirror group, so the agenda shows one row and any edit or delete fans out to every provider. Parsing, AI inference, and voice dictation all run entirely on the device — no server, no analytics, no tracking.

• Three-tier, fully on-device natural-language parsing: an instant regex parser, then Apple Intelligence (iOS 26+ guided generation), then a local TinyLlama running on llama.cpp — every tier resolving dates through the same shared logic.
• Write-once-everywhere sync: a MirrorStore groups the per-provider copies of each event, and a SyncCoordinator fans creates, edits, and deletes across EventKit, the Google Calendar API, and Microsoft Graph, naming any calendar a partial failure missed.
• Safe concurrent writes — Google/Graph etags are sent back as If-Match so edits made elsewhere fail loudly instead of being silently clobbered.
• Local voice dictation via NVIDIA Parakeet TDT v3 running on the Neural Engine (FluidAudio / CoreML); audio never leaves the phone.
• Home- and lock-screen widgets, a Siri App Intent for quick regex-parsed adds, and conflict detection that warns on overlap and suggests a free slot.
• 31 unit tests covering the parser, LLM response mapping, conflict checker, etag request factories, event payloads, and mirror-group dedup.

A barrier between you and the scroll, built around the five prayers.

A phone-discipline app for Muslims that shields distracting apps around each of the five daily prayers and makes every deliberate bypass cost something — a written niyyah always, and for Pro members a real ṣadaqah donation — with social accountability through halaqa circles. The spiritual core (Qur’ān, prayer times, qibla, tasbīḥ, adhan) runs entirely on-device; the cloud only handles auth, halaqa sync, subscriptions, push, and the server-side charge.

• Screen Time enforcement via Apple’s Family Controls / DeviceActivity stack — a monitor extension arms the shields around computed prayer windows, and dedicated ShieldAction and ShieldConfiguration extensions own the bypass button and the shield’s UI.
• A commitment-contract (Beeminder-style) payment model designed around Apple Guideline 3.1.1: the iOS app is a pure tracker that never shows a price, while a separate web portal vaults the card, holds the contract, and a Supabase edge function charges the customer when a violation is logged — the client never touches a PaymentIntent.
• Two full visual identities — Minimal (dark, data-forward) and Serene (warm, light, imagery-forward) — shipped from one codebase.
• Home- and lock-screen widgets, an in-app SFSafariViewController handoff to the portal with a sadd:// deep-link return, and ~36 Supabase migrations behind halaqa sync and bypass accounting.

Multi-tenant online and card-present donations, kiosk to payout.

A multi-tenant donation platform running at confer.sadd.app that takes gifts both online and in person on a card-present iPad kiosk, routing money to each organization through its own Stripe Connect account. A single Express backend serves every tenant; organizations self-onboard, configure funds and billing, and reconcile payouts from an admin portal, while a platform-owner dashboard registers tenants and sets the billing model.

• Per-tenant Stripe Connect payment pipelines with an embedded Connect dashboard portal, so each organization manages its own onboarding, payouts, and settings in isolation.
• A React Native iPad kiosk for card-present giving, with admin setup, restricted staff roles, and a sandbox simulation mode for training and testing.
• A single multi-tenant Express + Prisma/PostgreSQL backend with a complete REST API, rate limiting, and token revocation; CI runs backend type-checks, Jest integration tests, and a frontend build gate.
• React + Vite front end (Wouter routing, shadcn/ui primitives) driven by HSL design tokens, deployed serverless on Vercel.

Counter-swarm drone detection for when RF goes silent.

A product landing site for a passive, multi-modal counter-swarm detection system aimed at critical infrastructure, enterprise security, and SLTT agencies — detecting, classifying, and responding to coordinated drone swarms even when the radio-frequency spectrum is jammed, spoofed, or silent. The page frames the threat with real engagements and presents a zero-RF, acoustic-and-radar sensing approach.

• A live, animated SwarmCanvas that renders a passive multi-target scan with gold target-locks to visualize the detection concept in the browser.
• Narrative-driven product page built as a single-route React app, tuned for the counter-UAS buyer and search/social sharing (full OpenGraph and Twitter card metadata).

A fork-and-rebrand website + admin for any masjid — no database to run.

A modern, responsive website and self-service admin dashboard for a masjid or Islamic community center — originally built for the Islamic Center of Hattiesburg and structured so any masjid can fork it, swap in its own colors, prayer configuration, content, and donation forms, and deploy without standing up a SQL database. It ships with a public marketing site, live prayer-time calculation, and a full-screen TV display board for the prayer hall.

• A tiered remote-storage layer — Upstash Redis / Vercel KV or the GitHub Contents API, falling back to bundled JSON seeds — so the whole site runs with no PostgreSQL/MySQL to operate.
• Prayer times from the AlAdhan REST API on the main pages and the local adhan library on the /display board, all configured from one masjid config file.
• Stateless JWT auth in an httpOnly cookie for the admin dashboard, and donations via embedded Zeffy forms plus a LaunchGood link — no payment keys required.
• A dedicated /display TV board rendered without site chrome via middleware, for the prayer hall screen.

A desktop cotton-brokerage app, rebuilt as a web portal.

A cotton-brokerage management portal for a Pakistani firm that sources and brokers raw cotton, waste, and yarn to mills — a full port of a Windows .NET / MAUI desktop app to a responsive web portal at madinaenterprises.com, with complete feature parity across contracts, ginners, mills, deliveries, payments, and ledgers.

• Domain-exact business logic: maund/kg conversions, per-ginner commission defaults with per-contract override, payment-split holdbacks, and a payable amount always derived from recorded mill weight rather than bale estimates.
• A running ginner ledger rollup (contracts as debits; payments and delivery charges as credits) and delete-integrity checks that mirror the desktop app’s foreign-key guards, with atomic cascade deletes via a Postgres RPC.
• Supabase Auth with tightened row-level-security policies replacing a single hardcoded desktop credential, plus a global 401/JWT interceptor and a top-level error boundary.
• PDF, Word, and Excel statement exports carrying lot numbers, delivery charges, payment split, and weight-difference notes.

One deployment, two sites — retail and wholesale — no build step.

The static frontend for Estrah, a GOTS-certified organic cotton garment brand vertically manufactured in Punjab, Pakistan. Two distinct sites — a consumer retail storefront and a B2B wholesale portal — are served from a single Vercel deployment and split by hostname, built entirely in plain HTML, CSS, and vanilla JavaScript with no framework and no build step.

• Host-based routing in vercel.json rewrites supply.estrah.com to a separate wholesale portal while estrah.com serves the retail storefront, with shared static assets excluded from the rewrite so both domains can load them.
• A single-file retail SPA with JS-driven page routing across home, collection, product detail (gallery, colour/size selection, spec accordion, GOTS badge), and a working cart.
• A wholesale portal with line sheet, capabilities, supply-chain and certification detail, and a registration form.

Cryptopals solutions with a C# UI and a C++ test suite.

A full-stack application solving the Cryptopals cryptography challenges, pairing a C# user interface and application logic with the underlying cryptographic implementations and an automated test suite for regression safety.

• Cryptographic challenge solutions wired into a desktop UI rather than left as loose scripts.
• Automated unit testing of the core crypto functions via Google Test — the C++ implementations were validated under the test suite before the team moved the interface to C#.