Hasan Ahmed  /  Field Manual  /  Vol. 01
§03 — Selected Work
Last revised 2026-04-19 14:22 ICT
Copenhagen  —  Entry § 03  —  Selected Work
§ 03 — Selected Work  

A short inventory of things that shipped, with honest specs.

No cards, no screenshots, no hero shots. Projects are listed in reverse-chronological order with a terse description, a specifications block, and — where contract allows — a link to the source. Entries marked Contract / Private are production work under confidentiality; the description documents what can be said publicly.

§ 03.1 2024 — Aug 2026 Contract / Private

Internal platform · Full-stack contribution Apple — DMS & internal Vue/Nuxt applications

Ongoing contract work on several internal applications. The headline effort is a Document Management System (DMS) built on top of Box enterprise storage — a substantial module integrating Box into the application interface, with Node APIs brokering the storage layer and Laravel test suites covering the legacy surface.

Alongside the DMS I contribute to other Nuxt 3 / Vue 3 applications on the same platform — feature work across SSR and SPA surfaces, shared API-call management, state and cache layers, hydration correctness, and performance on long-lived sessions. The common thread is correctness at scale — teams depend on these primitives shipping without surprises.

NDA Host application, exact scope, and screenshots are confidential. What I can attest to: the work is production, ships on a regular cadence, and a senior reviewer has signed off on each merge.
→ Repository → Demo → Writeup → Reference on request
§ 03.2 2024 — Aug 2026 Contract / Private

Component library · Framework-agnostic Apple — internal component library

A separate, longer-lived surface from the DMS: an internal component library consumed by the DMS and other applications across the platform. My lane is framework-agnostic primitives — tokens, core Web Components, and Vue 3 / Nuxt 3 bindings that consume them — with a focus on hydration correctness, SSR parity, and a small, stable public API.

The library is its own application with its own release cadence. Getting a primitive right once means a dozen downstream apps don't each have to solve it — which is the entire point of a library.

→ Repository → Demo → Writeup → Reference on request
§ 03.3 2025 — Aug 2026 Concluded · v0.6.3

SDK · Package · Apple AI Chat Widget — embeddable, host-agnostic.

Also developed under the Apple engagement: a framework-agnostic chat widget built on the Web Components spec and StencilJS. Ships as a single <script> tag; renders identically inside Vue, React, Svelte, Nuxt, Next, or plain HTML — with no host-side glue.

Built as a test of a thesis: if your primitive has a public API, the framework shouldn't matter. Ships tokens as CSS custom properties, exposes slots and events, and adds precisely one runtime dependency.

→ Repository → Live demo → API docs → Design notes on request
§ 03.4 2023 — 2024 Shipped · Maintained by team

Web application · Full-stack AccTech Payroll — compliant payroll runs for U.S. SMBs.

Full-stack payroll platform for small and medium businesses in the United States. Handles salary structures, deductions, statutory reporting, and month-end closeouts. I owned the frontend from inception and contributed the bulk of the API — including the salary-calculation engine, which is the most-tested module I have written.

Payroll is unforgiving. A rounding bug becomes a late payment; a timezone bug becomes a legal problem. The project taught me more about correctness than any other engagement.

→ Product site → Repository → Case study → Architecture notes
§ 03.5 2022 — 2023 Archived · client-owned

Web application · Field operations AC Service — dispatch, inventory, and technician routing.

A field-service web app for a Dhaka-based air-conditioning service company: customer intake, ticket dispatch, technician routing, spare-parts inventory, and invoice generation. My first full-stack production deliverable. Unfashionable, thoroughly useful.

This is also where the habit of shipping fast started — small daily releases, customer feedback on WhatsApp, boring reliability as the headline feature.

→ Product site → Repository → Writeup → Reference on request
Shipped 22projects
Public repos 37on GitHub
Packages 4on npm
Published 1paper · IJEECS