Ali Houssein Ballout

The problem

Small distributors run orders, stock, invoices and accounting in separate tools, so numbers disagree. I wanted one system where a shipment, an invoice, a payment and a return always leave the books balanced.

What I built

• An accounting engine in plain JavaScript: every action is a pure function on one state object, so a failed action (credit limit, wrong role) leaves the original state untouched.
• Double-entry journals that always balance, FEFO lot allocation across two warehouses, partial shipments, returns that restore original cost, and bank matching that never posts cash twice.
• 18 connected screens, Arabic and English (RTL), USD base with EUR and LBP display, data saved in the browser with JSON backup and restore.
• 22 automated transaction tests (node:test) cover balanced journals, stock and receivable reconciliation, FEFO, expiry, tax rounding, returns and permissions.

Technology

• JavaScript (no framework)
• Accounting / ledger engine
• localStorage
• node:test
• Arabic RTL

The problem

Lebanese shops price in dollars but are paid in dollars and lira at once, and the connection drops. The register has to give the right change in two currencies and keep selling offline.

What I built

• Dual-currency maths: prices in USD, lira totals from an editable exchange rate (with history) rounded to the cash denomination, split payments across both currencies and generated change options.
• Offline-first PWA: a service worker caches the app shell (pages network-first, assets stale-while-revalidate). I tested reloading with the network off.
• Kitchen display and customer screen stay in sync with the register through shared storage events: no server needed.
• Owner / manager / cashier permissions, an audit trail with cashier risk scoring and cash-variance checks, QR menu, WhatsApp receipts, Arabic RTL.

Technology

• JavaScript (no framework)
• PWA + service worker
• localStorage
• USD / L.L.
• Arabic RTL

The problem

Enquiries arrived as vague messages, so every quote started with a long back-and-forth. I built a flow that turns an idea into a structured brief with an instant price.

What I built

• Voice-based scoping, instant pricing from one rate card, PDF proposals by email, plan approvals and owner notifications.
• Runs on its own domain and feeds this website: the studio site reads the same rate card, so prices exist in one place.
• Supabase tables with row-level security, five n8n workflows, an AI scope analysis that falls back to a rules engine when no key is set, rate limiting, 74 automated tests, Docker and a CI pipeline.

Technology

• Next.js 16
• React 19
• TypeScript
• Tailwind CSS
• Supabase
• n8n workflows
• OpenAI / Anthropic APIs
• SMTP email
• PDF generation
• Vitest
• Docker

The problem

A clinic has three people who need different views of the same visit. I wanted one codebase for the phone app and a browser demo, with the permissions enforced in the logic and not only hidden in the UI.

What I built

• Expo / React Native with TypeScript and expo-router, exported to the web with react-native-web, Arabic and English with Noto Sans Arabic.
• One domain module (appointments, queue, invoices, roles) shared by the API and by an offline store, so the browser demo works with fictional data saved only in the visitor’s browser.
• A Workers-style API over a SQL schema (Drizzle / SQLite): 24-hour sandboxes, hashed session tokens, rate limits and origin checks.

Technology

• Expo
• React Native
• TypeScript
• expo-router
• Drizzle ORM / SQLite
• react-native-web