I’m Numan, a full-stack mobile application developer using Agentic
AI, React
Native,
React
JS,
Next
JS,
TypeScript, Node,
Native Android, Native
IOS, and
the
web platform. I help startups and product teams ship
React Native app development,
mobile performance optimization, and
native Android/iOS integrations that hold up in production.
I also build open source packages on GitHub and write code
for apps that need to scale across mobile and web.
I’m based in Lahore, Pakistan, and I work remotely for global teams.
I have 25k+ reputation on Stack Overflow
I’m the author of react-native-compressor (200k+ weekly downloads) and 🔑
react-native-keys.
For teams that need one senior engineer to move fast, I focus on shipping mobile products that are stable, measurable, and easy to grow.
Build and ship new React Native apps with Expo, TypeScript, and a production-ready release process.
Improve startup time, rendering, image handling, animations, and app stability on iOS and Android.
Connect mobile apps to Node.js, Next.js, and API backends so the whole product moves together.
These are the React Native notes and service pages I would share with teams when they ask about performance, architecture, Expo, testing, releases, or hiring help.
A pillar guide for reducing startup time, improving rendering, and fixing the most common performance bottlenecks.
A decision guide for teams choosing the right React Native setup.
A practical guide to structuring production React Native apps for growth.
A practical guide to choosing local state, Context, Redux, Zustand, and more.
A debugging guide for memory growth, crashes, and cleanup issues.
A guide to modern architecture changes, migration tradeoffs, and production checks.
A practical page for teams that want faster mobile delivery with Expo and React Native.
A service page for teams that need Swift and SwiftUI support for production iPhone apps.
A service page for Kotlin, Compose, and production Android delivery.
A service page for founders comparing one codebase across iOS and Android.
A service page for people comparing React Native, iOS, and Android development help.
A service page for founders and startups who need a senior engineer for mobile delivery.
A practical guide covering secure storage, jailbreak/root detection, SSL pinning, and anti-tampering.
A guide for isolating crashes, regressions, and production issues faster.
A practical guide for protecting critical flows with unit, component, and end-to-end tests.
A guide to App Store and Play Store releases, CI/CD, and safer shipping workflows.
Here are some of my recent works on open source.
React Native, Expo, Native Android (Compose), Native IOS (SwiftUi), Algorithms, React, Next.js, Node.js, Express.js (MERN)
Javascript, Typescript, Kotlin, Java, Objective C, Swift, MVVM, Dragger, Hilt, Ruby, PHP, Asp, C#
Jest, IAP (Mobile Pay), Apple Pay, Stripe, Apollo GraphQL, AWS S3, web3.js
MongoDB, MySQL, Redis, SQL Server, SQLite
Crypto, Stocks, Aquanow, Alpaca, Leantech, Onfido, Plaid, Dwolla, Checkout2, Tabby, Tamara, Knet, QPay, Stc Pay, Subscriptions, Dexguard, Elastic Search, Typesense, Agentic AI, MCP, Machine Learning, LLM
CI/CD, Github Actions, Fastlane, Cherrypick, Reflog, Patch, Apply
Clevertap, Rudderstack, Adjust, WebEngage, Appboy(Braze), GA4, Datadog, Metabase, Clickhouse, Big Query
Advanced React Native skills and knowledge for building high-performance mobile applications.
• React Native Reanimated, React Native Skia and React Native Gesture Handler for Animation on 60FPS
• React Native Brownfield for integrating native app
• React Native Uniwind, React Native Restyle for styling
• HeroUi Native, Expo Ui for native components
• Hermes V1, React Native Nitro, TurboModule, Fabric Renderer
• Also having 33 JavaScript concepts knowledge
Happy to work on open source projects, make algorithms, and help programmers on StackOverflow.
| Plateform | Progress |
|---|---|
These are my Primary Skills, which I am currently working
Jest, IAP (Mobile Pay), Apple Pay, Stripe, Apollo GraphQL, AWS S3, web3.js
MongoDB, MySQL, Redis, SQL Server, SQLite
Clevertap, Rudderstack, Adjust, WebEngage, Appboy(Braze), GA4, Datadog, Metabase, Clickhouse, Big Query
Crypto, Stocks, Aquanow, Alpaca, Leantech, Onfido, Plaid, Dwolla, Checkout2, Tabby, Tamara, Knet, QPay, Stc Pay, Subscriptions, Dexguard, Elastic Search, Typesense, Agentic AI, MCP, Machine Learning, LLM
CI/CD, Github Actions, Fastlane, Cherrypick, Reflog, Patch, Apply
I already worked on a lot of projects, with the most different technologies to solve the most different kinds of problems.
React Native, Expo, Android, IOS
JavaScript, Typescript, Swift, ObjectiveC, Java, Kotlin, SwiftUI, Jetpack Compose, HTML, CSS
Jetpack Compose, XML, MVVM, Kotlin, Java, Dragger, Hilt, Dependency Injection, Retrofit, RoomDb
SwiftUI, UIKit, Swift, ObjectiveC, Alamofire, MVVM, RxSwift
Javascript obfuscation, Java obfuscation, Certificate SSL pinning, Jailbreak/Root detection, Secure Envs files through c++ and encryption, Anti-tampering measures, App Check for preventing backend apis abuse.
Class_base, Functional_components and Styled_components
Redux, MobX, Classes, Recoil, jotai, zustand & React Context API
Rest APIs, GraphQL, Firebase APIs, Socket.io, SignalR, PubNub
Places Auto Complete, Geocoding, Geolocation, Directions
Socket.io, SignalR, Firebase, Twilio
Calling/Streaming: Agore.io, Twilio & WebRTC
Firebase, Apns, OneSignal & PubNub
Google Crash Analytics, Firebase, Sentry & branch.io
Appboy, Clevertap
Elastic Search, Typesense, Algolia
Google AdMob, Facebook Ads
Facebook, Google, Instagram, Apple login
react-native-reanimted, react-native-skia, react-native-interactible
Turbo Module, Fabric renderer, JSI, Virtualization, Profiling, Flashlist, memo and useMemo, Performance monitoring through flipper plugins
React Js, NextJS, React Remix
Node js, Express, Puppeteer, Socket.IO, ASP WCF, Php
MongoDB, MySQL, MSSQL, SQLite, Postgresql, Redis
SQL, MongoDB Queries, GraphQL
Javascript [ES5, ES6, ES7, ES8] (Browser and Node.js), TypeScript, PHP, JSON, JSX
Flow, SASS, LESS
React, Redux, Ant design, jQuery, Axios, Lodash, Bootstrap, Styled components
Eslint, JSLint, Standard JS
Figma, Zeplin, Adobe XD, Sketch
GIT, SVN, CVS
Jest, Mocha, Chai
WordPress (plugins, themes and widgets)
Composer, Yarn, Npm, Bower, Make own custom package manager
Webpack, Metro
Docker, kubernetes, Heroku, Digital Ocean, Linode, Generic shared hosts, Vps Window server, Aws ubuntu instance, Firebase
Javascript , IOS(swift) , Android , MongoDB , AWS , Docker , destroy the structure of frameworks , Find loophole/vulnerability in coding level, next to move in protocol level or physical layer
Ecosystem building, Problem-solving, Protocols, Hacks, Algorithms
Php (wordpress, laravel, codeignitor), ASP .Net and MVC, C# window Forum, Unity, R Language, Android, java, scala, C/C++, Sql Injections
Babel, Storybook, REST, MVC, ORM, OOP, AWS (S3), Functional programming, SOLID, Natural Language Processing, Scrum, Continuous Integration, Continuous Delivery, Progressive web apps, Performance, Usability, Accessibility, SEO, Terraform
I already had the opportunity to work on awesome companies with awesome people.
January 2022 – Currently Working
• Developed a multicategory grocery and food delivery app from scratch using React Native and IPA web using Next JS, attracting millions of users with thousands of daily orders
• Implemented complex payment systems including Apple Pay, credit/debit pay, Tap Pay, Wallet Pay, and others
• Tech Stack: React Native, Expo, Next.js, Node.js, JavaScript, TypeScript, Java, Kotlin, Objective-C, Swift, Docker, GraphQL, TypeSense, Elastic Search, Socket Stomp, JNI, Detox
March 2021 – January 2022
• App based Platform where we can buy and sell Products (such as Car, Furniture), Services and properties
• Worked on the mobile app using React Native as well as some services like chat service on the backend using node JS
• Tech Stack: React Native, Expo, React JS, Node JS, JavaScript, Typescript, Java, Kotlin, ObjectiveC, Swift, Socket.io Redis, Fastlane, CI/CD, Kubernates, TerraForm
February 2019 – March 2021
• Have many white label apps which covered Buy one Get One, Hotels, Travels and Retail, Al Futtaim was one of our clients
• Along Mobile app Development, We Also Developed Web Portal which can make apps in 5 minutes by selecting modules
• Worked on The Entertainer, Chalhoub Entertainer and multiple white labels Mobile apps using react native
• Tech Stack: React Native, Expo, React JS, Node JS, JavaScript, Typescript, Java, Kotlin, ObjectiveC, Swift, Saas, MongoDB
January 2018 – February 2019
• Build Zirtue Mobile app using React Native along with backend using Node JS and Web Portal Admin Panel using React JS
• Also Build couple of apps and web portal like Workout Timer app Using RN etc
• Tech Stack: React Native, MERN, Typescript, Java, Kotlin, ObjectiveC, Swift, Redux, Firebase, Dwolla, Plaid, Stripe
Jan, 2017 - Dec, 2017
Worked on React Native, React js, Node js.
Jan, 2017 - Dec, 2017
Worked on React Native, React js, Node js.
now I am learning every day. I try to learn something new every single day.
January 2014 – September 2018
2012 - 2014
2010 - 2012
Since my career's beginning, I always used open-source tools. So, why not to contribute with some open-source tools?
• Having 25k+ Reputation on StackOverFlow
• iPhone 15 featured my "React Native (Mobile) App Dynamic Island (Notification)" on its official website
• Contributed into React Native Core, Expo Core and React Native Reanimated
• Author of React Native Compressor and React Native Keys Open source packages
• Have more than 200k+ weekly downloads for my one of React Native Package
Most of my work runs on closed environments, or under NDA (confidentiality agreement). So I can not show most of the projects I worked on. But here, I'm showing some of the public projects. Apps list are too much longer,so I am just sharing some of it.
Explore full project case studies: Zirtue, EasyQuran.ai, CHECK24, Mein dm, Dola, EasyPark, Workout Timer, Chalhoub ENTERTAINER, ENTERTAINER X Circles.Life, Roumaan, The Emirates Tourism, One X Platform, Masterpiece, Wibb, Shobbak, IDIL Admin, and all portfolio projects.
Ninja Mobile App -> 60k+ Reviews and 4.8 rating. Unicorn 1 Billion USD company. Ninja App is handling Four Verticals deliveries: Grocery (Super Market) like Flink, Restaurant, Beauty, Pharmacy (Medicines + Doctor consultation). Order groceries via our app and in 30 minutes we'll deliver your shopping right to your door.
The ENTERTAINER is the moneysaving app that’s packed with the 2-for-1 offers everyone wants.
Shobbak app is an online flea market from KSA. This app provides an open space to sell all kinds of goods, new or used.
Wibb manage the US Party System through app.
Workout Timer is fully customizable interval timer that dictates each exercise. Create as many different sets as you want and how many rounds you want to do them for. Great in the gym, at home, or outdoors.
Chalhoub Group ENTERTAINER will transform the way you enjoy your experiences, with unbeatable Buy 1 Get 1 Free offers in dining, beauty, retail, everyday services, entertainment and fitness.
Masterpiece manage Employee Shifts and tasks.
The ENTERTAINER X Circles.Life App brings you unbeatable value with thousands of Buy 1 Get 1 Free dining, leisure, wellness, entertainment and hotel accommodation offers across Singapore, Malaysia, Bali, Hong Kong and London.
Roumaan.com brings to you online shopping like never before. Download the app & enjoy the best deals in Middle East.
The Emirates Tourism app brings you great value with ‘Buy One Get One Free’ and ‘Discount Offers’ across attractions, hotels and restaurants in Unites Arab Emirates..
One X Plateform is an App Builder which enable non-technical person make apps (PWA, Expo, Expokit) through combining module from the web portal.
A few quick answers for people looking for a senior React Native developer or mobile app engineer.
Everything from new app builds to app store releases, performance work, backend integration, native modules, and debugging production issues.
Yes. I use Expo when it fits the product, and I can go native with Kotlin, Swift, Compose, or SwiftUI when the app needs deeper platform control.
Yes. I can help with the mobile app itself, the technical decisions around it, and the public pages that explain the product clearly to future users and teams.
This site is not only a portfolio. I use it to explain how I approach React Native, Expo, native Android and iOS work, performance fixes, release quality, and full-stack product delivery.
My preference is to start with the product constraint, then choose the technical approach. A mobile app usually has competing pressures: delivery speed, app size, startup time, offline behavior, platform-specific details, analytics, release risk, and the cost of maintaining the code after the first version ships. Good React Native work keeps those pressures visible instead of hiding them behind library choices.
When I review a codebase or plan a new build, I look for the parts that will create the most operational risk: slow screens, unclear state ownership, fragile navigation, native modules without a release plan, missing test coverage, oversized images, and app-store workflows that depend on manual steps. Fixing those problems early is usually cheaper than trying to recover after users start reporting crashes or performance issues.
That is also why the pages on this site link to each other. Architecture affects performance, testing affects release confidence, Expo choices affect native integration, and component-level decisions can show up later as accessibility, debugging, or maintenance problems. The goal is not to make the app look technically impressive. The goal is to make it stable, understandable, and easy for a real team to keep improving.
I usually work best with teams that already have a product direction and need stronger engineering execution: a cleaner React Native architecture, a difficult Expo or native integration, a performance problem that is hard to reproduce, or a release process that needs fewer surprises. My background across mobile apps, backend APIs, Next.js surfaces, and open source packages helps me connect those decisions instead of treating each screen or ticket as an isolated task.
If you are reading this as a founder, product lead, or engineering manager, the useful detail is not only the list of technologies. The useful detail is whether the engineer can notice risk early, explain tradeoffs clearly, and keep shipping without turning the codebase into something fragile. That is the standard I try to bring to mobile product work.
I also care about the parts of mobile work that are easy to ignore during a first build: crash reporting, app size, image handling, permission flows, API retries, release notes, store review details, and the small platform differences that make iOS and Android feel different in production. Those details decide whether a product feels stable after launch.
Most of my public writing here comes from problems I have seen in real apps. Some pages are about hiring and delivery, some are about Expo or React Native architecture, and some are about smaller UI details like search bars, progress bars, forms, and accessibility. Together they show how I think through product engineering rather than only listing projects.
For new work, I prefer clear scope, short feedback loops, and measurable release goals. That can mean a focused MVP, a rescue pass on an existing app, or a few weeks of targeted help around performance, testing, native modules, or app-store delivery.
I have learned that mobile product work goes better when the same person can understand the screen, the API, the release pipeline, and the native platform behavior behind it. A slow checkout, a camera permission issue, a broken deep link, or an image upload problem rarely belongs to only one layer. The value comes from tracing the full path and fixing the actual cause.
When I join a project, I try to make the next decision easier for the team. Sometimes that means writing a feature. Sometimes it means removing a risky dependency, simplifying state, documenting a build process, or showing why a native implementation is worth the extra work. Small decisions like that compound into an app that is easier to support.
This homepage links into my guides because the writing gives more context than a resume can. If you want to know how I think about React Native performance, Expo workflows, testing, architecture, component behavior, or production debugging, those notes are the best place to start before a call.
I also keep the site personal on purpose. I am not trying to look like a large agency. I want the page to make it clear what I actually do, where my experience is strongest, and how I can help when a team needs senior mobile engineering without adding a heavy process around the work.
A lot of my strongest work happens in the middle of a project, when the first version already exists and the hard questions start showing up. Why does one screen feel slow on Android but not iOS? Why does a release work locally and fail in CI? Why does a package upgrade break only one native module? Why does a flow look simple in design but become fragile once permissions, deep links, analytics, and offline states are included?
Those are the situations where experience matters. I like tracing the problem through the codebase, making the smallest useful change, and leaving the team with a clearer system than before. That might mean profiling a screen, rewriting an upload path, isolating a native crash, reducing render work, or turning a fragile manual release into a checklist the team can repeat.
I am also comfortable working close to product decisions. A technical answer that ignores the timeline, budget, user behavior, or team size is not very useful. When a founder or product lead asks whether to use Expo, bare React Native, native Android, native iOS, or a web surface, I try to explain the tradeoff in terms of the next release and the maintenance cost after launch.
For existing teams, I can usually add value without taking over the whole project. I can review architecture, ship a feature, unblock a build, fix a performance issue, write targeted tests, or help the team make a cleaner plan for the next few releases. The scope can be small if the problem is specific, or broader if the app needs deeper stabilization.
For new products, I care about getting the foundation right without overbuilding. That means choosing a stack the team can actually maintain, keeping navigation and state predictable, avoiding unnecessary native complexity, and setting up releases early enough that store delivery does not become a last-minute surprise.
Open source has shaped how I work too. Maintaining packages used by other developers teaches you to think about edge cases, documentation, compatibility, and support. It also makes you more careful about breaking changes because real apps depend on the code after it leaves your machine.
My preference is simple: build the product in a way that lets the next engineer understand it. Clear naming, sensible boundaries, useful logs, small components, predictable data flow, and enough tests around the important parts make a bigger difference than chasing every new library.
If you are comparing engineers, look for someone who can talk about risks without making the project feel heavier than it needs to be. The best mobile work is practical: it ships, it performs well enough on real devices, it is recoverable when something breaks, and it leaves the team more confident about the next release.
Home Office:
This is my home office as i am doing remote job