Available for work
Let’s talkMobile Product Engineer · Bengaluru, UTC +5:30
React Native and Expo, across iOS and Android. Two startups, two apps built from an empty repo — both shipped, and one live in production right now.
Live today: App StoreGoogle Play
About
I build apps for phones — the kind that earn a place on someone’s home screen and get opened without thinking.
What pulled me into mobile is how real it is. You write something one week, and the next it is running in a stranger’s hand, on a patchy connection, on a device three years older than the one you tested on. There is no staging environment to hide behind, and I love that. It keeps the work honest.
I’ve built two apps from an empty repo. The first was at a startup where I was part of the founding team; the second is live on the App Store and Google Play. In both cases, I owned the app from the first commit through the first release and everything that followed.
The part I enjoy most is the craft. Making a list scroll smoothly on cheap hardware. Cutting a load time from three seconds to one. Staying with a crash until it finally admits what it is. These problems have real answers, and when you get one right you can feel the difference in your hand.
Outside of work, I travel whenever I get the chance. I’d rather see a place with my own eyes than read about it.
Based in Bengaluru. Worked with teams across the globe.
What I do
The app exists, but whoever built it has moved on, or it has stalled. I learn the codebase, tell you honestly what state it is in, and take over shipping it.
Users are hitting crashes you cannot reproduce, or the app is slow on the phones people actually own. I work from real crash and trace data rather than guesses.
Signing, provisioning, TestFlight, App Store Connect, Play Console, review, and separate dev, staging and production builds so nothing untested reaches a real user. The part that stalls launches and has nothing to do with your product.
New screens and flows inside an app that already has users, wired to your backend, without leaving a mess for whoever comes next.
Ongoing engineering ownership: releases, SDK upgrades, store policy changes, and the crashes that show up when the OS updates. Monthly, not per-ticket.
Marketing sites, landing pages and internal tools in React and Next.js, built to load fast rather than to win awards. Useful when the app and the site need to say the same thing.
Work
Find a charger, plan a trip around one, book and pay for a session. Built from an empty repo and live on both stores, where I own mobile end to end — releases, crash and ANR triage, performance on real Android hardware, and the SDK upgrades that keep it shippable.
Purchases, refunds, subscriptions and shipments pulled into one place. There was no mobile app when I joined; I built it in React Native and led its release to the Play Store, then owned the frontend for a year and a half — deep linking, the data layer, charts, secure file uploads, a caching pass that cut load times from about three seconds to one, and push through FCM.
Upstream
Sentry was silently dropping every log and span on iOS with React Native 0.86 and above, while still reporting HTTP 200 — so error reporting looked healthy and collected nothing. I traced it to an unreliableperformance.timeOrigin, reported it with a reproduction, and Sentry shipped the fix six days later.
Fixed in 8.25.0“Prevent silently dropped logs and spans on iOS with React Native ≥ 0.86 caused by an unreliable performance.timeOrigin”
Skills
From an empty repo to something that runs on both platforms.
The part that stalls launches and has nothing to do with the product.
Knowing what is actually happening on other people's phones.
Everything after launch, which is most of an app's life.
Backend & web
Languages
Experience
Jul 2025 — present
RangeNow, iOS and Android
Dec 2023 — May 2025
Founding team; owned the mobile frontend
Engineering, Jamia Millia Islamia, New Delhi.
Get in touch
The more you can tell me up front, the more useful my first reply will be. Or just email hello@shoyeb.dev.