About the Author
native-update is designed, built, maintained, and supported by Ahsan Mahmood — a senior full-stack engineer based in Pakistan, specialising in Capacitor, React, Laravel, and Firebase. The plugin is the consolidation of update flows shipped across multiple production apps where rolling out fixes through the App Store and Play Store review queues was too slow for the kind of bugs users actually care about.
If this plugin saved you a sprint, a quick mention to a teammate, a star on the docs repo, or a recommendation on LinkedIn is the most valuable kind of feedback. Hiring me for a Capacitor / React / Laravel / Firebase project is the second most valuable.
Reach me
| Channel | Address |
|---|---|
| Personal site | aoneahsan.com |
| aoneahsan@gmail.com | |
| linkedin.com/in/aoneahsan | |
| GitHub | github.com/aoneahsan |
| npm | npmjs.com/~aoneahsan — 50+ published packages |
| +92 304 6619706 | |
| Phone | +92 304 6619706 |
I respond to email and LinkedIn DMs within 24 hours on weekdays.
What I do
- Capacitor plugin development —
native-updateis one of several plugins I maintain. I have shipped plugins covering analytics, biometrics, file storage, deep linking, in-app purchases, and OTA updates. - React + TypeScript front-ends — TanStack Router / Query, Radix UI, shadcn, react-hook-form + Zod, performance-first patterns.
- Laravel back-ends — REST + GraphQL APIs, Nova admin panels, Sanctum / Passport auth, Horizon queues, multi-tenant architectures.
- Firebase — Firestore data modelling, security rules, Authentication (with custom claims), Cloud Functions, Hosting, App Hosting.
- Capacitor mobile apps — full lifecycle from
cap initthrough Play Store and App Store submission, including the boring but critical bits (privacy policies, data-safety forms, certificate management).
Hire me
If you are building a Capacitor app and your team is feeling the same pain that motivated this plugin — long review queues, manual signing pipelines, brittle update flows — I do consulting and project work. Email or LinkedIn is the fastest way in.
For one-off support around native-update itself, opening a GitHub issue is the right channel; I respond there too.
Other open-source work
A small selection of packages I maintain on npm under @aoneahsan:
native-update— this plugin- (Batch 10 of this docs site will deep-link a curated list of the most useful sibling packages)
Why I publish documentation as a separate repo
The plugin source code lives in a private GitHub repository while the project matures and the SaaS commercial side is built out. Documentation should not be gated by that decision — so this docs site lives in its own public repo at aoneahsan/native-update-docs.
That separation has a side benefit: search engines and AI assistants index public GitHub repos heavily, and the public docs repo plus this hosted Docusaurus site give the plugin two distinct discoverability surfaces beyond the npm page.