Ahsan Mahmood — full-stack developer, Lahore. 23 products shipped.
Full-stack software developer with 8+ years' experience. One React and TypeScript codebase becomes a web app, an Android app and a browser extension. 23 live products, 25 npm packages. Available for client work.
Eight years, six roles
Building and maintaining my own products full time — 23 live across the web, Google Play and the extension stores, 25 packages published to npm, four of them open source. Available for client projects and contracts.
Open Source & Community Projects Developer
From pixel-perfect UI work in January 2018 to owning delivery end to end — and, since March 2026, running my own products full time and taking on client projects.
- Download the full CV
- Jan 2018 — May 2018
Where it started — pixel-perfect interfaces in HTML5, CSS3 and JavaScript across multiple web projects.
Frontend Developer
Custom themes and plugins, advanced custom fields, and site maintenance for a range of clients.
WordPress Developer
Owned delivery of SaaS features across web and mobile with React, Node.js, TypeScript and Apollo GraphQL. Built the Slack and Microsoft Teams integrations. Led implementation planning and code review.
Senior MERN Stack Developer
Built a custom management system on Laravel and Angular, added PWA capability, and delivered responsive UI against design specifications.
Web App Developer
Delivered client products on MERN and MEAN, native and hybrid mobile apps, and a production Manifest V3 browser extension. Owned execution from requirements to deployment.
Team Lead, SaaS App Developer
Certifications
- Virtual University of Pakistan · 2018–2022
- BSc Software Engineering
Govt. Shalimar Graduate College, Lahore · 2016–2017
Education and certifications
Your existing web app packaged, hardened and taken through Play Console review.
Android apps with Capacitor
Data model, security rules, interface, mobile packaging, store submission, and the documentation that has to exist afterwards.
A product, end to end
Manifest V3, built once for Chrome, Firefox and Edge, including the store submissions.
Browser extensions
Regular review on your team's pull requests, or one-to-one work with a developer.
Code review and mentoring
Audit first — code quality, security, performance — then a prioritised roadmap and the work itself.
Taking over an existing codebase
React and TypeScript front ends, from a marketing site to a multi-tenant admin panel.
Web app development
Pricing scales with scope, complexity and timeline. You get a firm quote after the free consultation, once the deliverables and integrations are scoped.
- What does a project cost?
Small features ship in 1–2 weeks, MVPs in 4–8 weeks, full production apps in 8–16 weeks. Most projects start within 48 hours of acceptance, with weekly progress demos and milestone-based delivery.
- How long does a project take?
Questions I get asked
Yes. An NDA is signed before any sensitive details are shared, and full IP ownership of delivered code transfers to you on final payment. Contracts cover confidentiality, deliverables, payment terms and post-launch support.
- Do you sign NDAs and transfer IP?
WhatsApp, usually within hours on a working day. Email is monitored too and answered within one business day.
- What is the fastest way to reach you?
Yes, and it is a common engagement. It starts with an audit covering code quality, security and performance, and produces a prioritised roadmap before any code is written.
- Can you take over an existing codebase?
Pakistan Standard Time, UTC+5. Meetings are routinely scheduled across US, UK, EU and Australian working hours.
- What time zone do you work in?
- Available for client work
- Download CV
- Not taking new work
- See the work
- Start a project
Full-stack developer. I ship products, not prototypes.
English — full professional proficiency · Urdu — native
Languages
I don’t do design-only engagements, native iOS (no Apple Developer account yet), blockchain work, or projects where the budget assumes an offshore rate for onshore expectations. Saying this now saves us both a call.
What I don’t do
The rest are client or commercial work, so their code stays private — I would rather say that plainly than imply otherwise.
One storage API across eight backends, zero dependencies
Reclaim disk space on macOS from the command line
- The same idea, for Linux
- Inspect what a machine is actually running
- Open source
Two of the twenty-five are load-bearing
Most of my packages exist because a project needed them twice. These two are used across every app I ship, which is the only endorsement I can honestly give them.
Over-the-air updates for Capacitor apps — bundle signing, staged rollout, and automatic rollback when a bundle fails to boot twice.
One storage API across localStorage, IndexedDB, cookies, the URL, native Keychain and Keystore, SQLite and the filesystem. Zero dependencies.
A free 30-minute call first, to scope what you actually need. If I am not the right person for it, I will tell you on that call.
Weekly progress demos against milestones, not a status report. You see the thing running.
An NDA before any sensitive detail is shared, and full IP ownership of delivered code transfers to you on final payment.
Small features ship in 1–2 weeks, an MVP in 4–8, a full production app in 8–16. Most projects start within 48 hours of acceptance.
You get the repository, the deployment, the store listings and the documentation. Nothing stays on my machine.
How I work
- Docs sites
- one per product that needs one
- Extension stores
- Chrome, Firefox, Edge
- How the range is possible
One codebase, five places people can install it
This is the thing that lets one person keep twenty-three products alive. The web app, the Android build and the extension are the same React and TypeScript source, packaged three ways. Each ribbon below is scaled to the real number of live listings on that surface.
- npm packages
- four of them open source
- Google Play
- published Android listings
- ONE CODEBASE
- Live listings
- Note
- Surface
- Total
- Web apps
- deployed and reachable
- Services
What you can hire me for
- See every service
- Android
- Chrome
- Identifier
- Live
- Stack
- Surfaces
- Web
- Open the live site
Web PWA, published Android app, and a Chrome extension
One React + TypeScript codebase behind all three
A BYOK “Growth Suite” tier and a white-label licence system
- categories
- surfaces
- tools
- Also
- When the target genuinely suits them better
- Backend
- Only where a server is genuinely required
- Default technology choices by layer
- Default
- Layer
- Why
- Data
- Free tier that survives a real launch
- Extensions
- Three stores from one build
What I actually build with
One component layer that ships to three targets
Not a badge wall. This is the set I reach for by default, and what each one is for.
- Mobile
- Native packaging without a second codebase
- Based in
- Lahore, Pakistan · UTC+5
The first call is 30 minutes and free. Bring what you are trying to build, roughly when you need it, and a budget range — I will tell you honestly whether I am the right person for it.
Let’s build it
- Response time
- Hours on WhatsApp, one business day by email
- WhatsApp
- Working with
- Clients worldwide, remote
Not a client list — these are the products I designed, built and shipped myself, across the web, Google Play and the Chrome, Firefox and Edge extension stores.
Free-tier Firebase or Supabase, processing done in the browser wherever the work can happen there, and no paid service in the critical path. That is how twenty-three products stay live without a monthly bill behind them.
- A constraint I work under on purpose
A product should cost nothing to run until it earns
predictable running costs, no surprise invoice, an app that survives being ignored for a year
architectures that only make sense at scale you do not have yet — and I will say so before we start
- Rules out
- Mar 2026
- Jul 2022
- Mar 2020
- Oct 2018
- Jun 2018
- Jan 2018
https://aoneahsan.com