Web Development
End-to-end builds: database schema, server logic, templating, and a frontend that behaves the same on a 1440px monitor and a five-year-old phone. I write code that the next developer can read.
Available for select projects — 2026
I build digital products that matter.
Full-stack developer working across PHP, JavaScript and design systems. I take rough ideas and turn them into products that load fast, read clearly and hold up under real use.
PHP · JS · MySQL
98 Lighthouse
Design systems
01
About
Developer first. Designer by necessity.
I've spent the last several years building for the web — from small brochure sites to internal tools that a team depends on every day.
Most of my work sits at the point where engineering meets interface — the place where a component has to be both semantically clean and genuinely pleasant to touch.
"Ship the version that works, then make it feel inevitable." Working principle
I started with PHP because it was the shortest path from an idea to something a real person could open in a browser. That hasn't changed — it's still the most direct way I know to build a system that just runs.
Over time the work widened: frontend architecture, animation, design systems, accessibility, and the unglamorous performance work that decides whether anyone stays past the first three seconds.
I care about the details that don't show up in a screenshot — how a form fails, how a page behaves on a mid-range Android over 3G, how keyboard navigation feels. Those are usually the difference between something that demos well and something that lasts.
I'm based in Faisalabad and work remotely with teams and founders across time zones.
0+
Years building
for the web
for the web
0+
Projects designed
& shipped
& shipped
0
Clients & teams
collaborated with
collaborated with
0%
Typical Lighthouse
performance score
performance score
02
Services
What I actually do for people.
Six areas of work. Most engagements combine two or three of them.
Backend & APIs
Structured application logic, authentication, role systems, and REST endpoints that are documented, versioned and predictable. Includes the boring parts: validation, rate limits, error handling.
Frontend Engineering
Component architecture, state management, motion, and interaction design. The goal is never "animated" — it's "obvious". Everything should feel like it responded before you finished clicking.
UI Implementation
You have a Figma file. I turn it into a real interface — pixel-accurate where it matters, sensibly adapted where the design didn't account for a 320px screen or a 40-character name.
Performance & Audits
Diagnosis and repair of slow sites: query profiling, asset pipelines, render-blocking resources, Core Web Vitals. Usually measured, always verified before and after.
Integrations & CMS
Payment gateways, CRMs, email platforms, third-party APIs, and WordPress or custom admin panels your team can actually operate without calling me every week.
03
Toolkit
Tools I reach for by default.
Comfortable is not the same as expert. These are the ones I use weekly.
PHP Daily
JavaScript Daily
HTML5 Daily
CSS3 Daily
MySQL Daily
Laravel Regular
Git Daily
REST APIs Regular
WordPress Regular
Three.js Occasional
GSAP Regular
Figma Regular
Node.js Occasional
Linux / Nginx Regular
04
Experience
Where the work has taken me.
Sample entries — replace with your actual roles and dates.
2024 — Present
Senior Full-Stack Developer Independent / Freelance
Designing and building web products end to end for founders and small product teams. Typical engagements run six to fourteen weeks and cover architecture, build, and a handover that actually gets used.
2022 — 2024
Full-Stack Developer Company Name
Owned a customer-facing dashboard used by several thousand accounts. Rebuilt the data layer, cut average page load from 4.1s to under 1.2s, and introduced a component library the team still uses.
2021 — 2022
Frontend Developer Agency / Studio
Built marketing sites and campaign pages for agency clients. First real exposure to motion design, and where I learned that most animation should be invisible.
2020 — 2021
Junior Developer First Role
Maintenance, bug fixing and small features across a portfolio of PHP sites. Unglamorous, and probably the most useful year of my career so far.
05
Selected work
Things I've built and would build again.
A mix of client work and product experiments. Case details are summarised.
Featured
2025
Web Application
Ledger — Invoicing platform
Multi-tenant billing with recurring invoices, regional tax handling and a client portal built to need zero onboarding.
2025
UI/UX · Frontend
Northwind — Design system
Consolidated four drifting front-ends into one documented library of 38 primitives with token-driven theming.
2024
Web Application
Atlas — Inventory control
Replaced three conflicting spreadsheets with one audited inventory system and a mobile scanning flow.
2024
Frontend · Editorial
Meridian — Editorial site
A reading-first publication built on typography, with under 9 KB of JavaScript shipped to the browser.
2023
Frontend
Signal — Analytics dashboard
Canvas-rendered metrics at 40k points, with a full keyboard and screen-reader path through every chart.
2023
PHP · CMS
Harvest — CMS for a studio
A block-based content system with six content types, an exact preview, and no plugin dependency.
06
Process
How a project actually runs.
Six stages. Not every project needs all six at full weight, but nothing gets skipped entirely.
Discover
A conversation, then a written brief. I need to understand the constraint before the requirement — budget, deadline, or the person who has to maintain it afterwards.
Strategy
Scope, architecture, and what we're explicitly not building. Saying no to two features now saves a rewrite in month three.
Design
Structure and hierarchy first, surface second. If it doesn't work as a wireframe it won't work with a gradient on top.
Build
Working software in reviewable increments. You see progress weekly, not at the end. Everything is version controlled from day one.
Refine
Real content, real devices, real network conditions. This is where performance gets measured and interaction details get tuned.
Launch
Deployment, monitoring, and documentation. Then a handover call so you're not dependent on me for routine changes.
07
Feedback
What people say afterwards.
Sample content — replace with real quotes and permission before publishing.
08
Questions
The things people ask first.
If yours isn't here, the contact form is the fastest route.
Mostly web applications, marketing sites with real engineering behind
them, CMS builds, and performance rescue work. I'm a poor fit for
projects that need a full creative agency — brand strategy, print,
video — and I'll say so rather than pretend otherwise.
A focused marketing site runs three to five weeks. A web application
with authentication, a database and an admin layer is usually eight to
sixteen weeks depending on scope. I give a range after the discovery
call, not before — anything else is guesswork.
PHP (including Laravel), MySQL, JavaScript, HTML and CSS as the core
stack. On the frontend I use vanilla JS where it's sufficient and
reach for GSAP or Three.js when the work genuinely calls for it. I'll
use whatever the project already runs on rather than forcing a rewrite.
A shared channel (Slack, email, or whatever you already use) plus a
weekly written update with what shipped, what's next, and anything
blocking. You'll have a staging URL from the first week so you can see
progress rather than wait for a demo.
Two structured revision rounds per stage. In practice, most feedback
lands in the first round because you're reviewing something real
rather than a mockup. Additional rounds are quoted at an hourly rate
so there are no surprises on either side.
Yes — a monthly retainer covering dependency updates, security
patches, backups monitoring and a set number of small changes. Plenty
of clients take it for six months after launch and then drop it once
their team is comfortable.
A short description of the problem, any existing brand or design
assets, a rough budget range, and who the decision-maker is. That's
enough for a first call. I'll follow up with a written scope before
any money changes hands.
I usually keep one or two slots open for new work. Send a brief
through the contact form and I'll tell you honestly when I could
start — including if that's two months out.
09
Contact
Tell me what you're trying to build.
A few sentences is enough to start. I reply to everything within a day or two, including the ones I can't take on.
Faisalabad, Punjab, Pakistan
10
News & Blog
Notes on code, architecture & craft.
Field notes, engineering deep-dives, and interface case studies on modern full-stack development, performance optimization, and design systems.
Backend · Laravel
7 min
Scaling Laravel Eloquent for High-Throughput APIs
Eliminating N+1 query bottlenecks, deferred eager loading, and query pipeline caching to process 12,000 req/sec with minimal memory footprint.
Read article
Frontend · Motion
5 min
Crafting Micro-Interactions with GSAP and CSS Houdini
Why the best animations are felt rather than noticed: timing curves, spring physics, and building GPU-accelerated interaction layers.
Read article
Performance · Core Vitals
6 min
Sub-Second First Paint: Core Web Vitals in 2026
Practical audits that cut INP by 65% and brought LCP under 800ms: font synthesis, speculative prerendering, and zero-JS critical paths.
Read article
Design Systems · Tokens
8 min
Building a Resilient Design System Across Multi-App Teams
Moving from fragmented component libraries to 38 primitives governed by tokenized typography, space scales, and automated dark modes.
Read article
Creative Tech · Three.js
9 min
Interactive WebGL: Real-Time Shaders for Landing Pages
A developer-friendly introduction to fragment shaders, custom raymarching, and rendering performant 3D geometry without battery drain.
Read article
Architecture · Database
10 min
Multi-Tenant Architecture: Isolation vs Shared Schemas
Comparing single-database schema separation vs separate tenant databases in high-concurrency SaaS applications.
Read article
UI/UX · Editorial
5 min
Typography as Interface: Reading Flow Trumps Decoration
How optical sizing, rhythmic vertical margins, and fluid clamp formulas transform plain text into an immersive reading experience.
Read article
Infrastructure · Queues
7 min
Pragmatic Event-Driven Pipelines with Redis and Queues
Decoupling heavy export jobs, webhooks, and third-party syncs using Redis streams, supervisor daemons, and dead-letter failovers.
Read article
Accessibility · A11y
6 min
Screen-Reader First: Building Truly Accessible Web Apps
Navigating focus traps, live announcement regions, and keyboard contracts so assistive tech users experience the app without friction.
Read article
Engineering · JavaScript
6 min
The Vanilla Advantage: Writing Fast, Zero-Dependency JS
When frameworks are overkill: building reactive state, modal drawers, and custom sliders in 4KB of modern standard JavaScript.
Read article
Have something that needs building properly?
Whether it's a new product, a rescue mission on an existing one, or just a second opinion — I'd like to hear about it.