Anandkumar Patil
Senior React Native DeveloperSix years building cross-platform apps in React Native. I’ve taken apps from an empty repository to the store, from the store to seventy-five thousand members, and from JavaScript down into Swift and Kotlin when the JavaScript ran out.
Currently Lead React Native Developer at Datman, where the payment apps I built from scratch are architected for over a million transactions a day. On my own time I design and ship apps under Apphive — five are live on the App Store and Google Play.
Five have public store listings. Two more are still being built, and they get a link to their own site rather than a store badge that doesn't exist yet.
Pulse diagnostics · hardware
A React Native app paired to a connected pulse-reading device. It captures the waveform, plots it, and turns pulse wavelengths into a health report a practitioner can hand to a patient. I took it from greenfield to production and owned Payments, Patient Management and report generation, plus the release automation that put each build in front of users.
React NativeExpoReduxRedux-Saga
AI haircut try-on
A native SwiftUI app that previews AI-generated hairstyles on your own selfie before you sit in the chair. I built all of it: the SwiftUI client, the Supabase backend on Postgres and Edge Functions, RevenueCat billing, and a server-authoritative quota with monthly and lifetime caps that a modified client can't argue with. A deleted account is soft-deleted, so someone who comes back still has the Pro they paid for.
SwiftUISupabasePerfectCorp YouCamRevenueCatSign in with AppleMixpanel
AI Bible study
An AI Bible companion: verse search, contextual explanations, and study you can hold a conversation with. The interesting parts are underneath — streaming chat over the Claude API with prompt caching, verse citations that resolve while the response is still arriving, and a reading-plan engine on Supabase.
React NativeExpoClaude APISupabaseExpo PushRevenueCat
Course platform
A tutorial platform for an acupressure practitioner and his students. The hard part was video: tokenised URLs into encrypted local storage, three quality tiers, and a download pipeline that finishes 90.2% of the time across ten thousand-plus downloads a month. Full offline playback and live sessions for 2,000+ concurrent attendees are in build.
React NativeExpoEncrypted local storage
Freelance marketplace
Job discovery and job posting for freelancers. I was the first engineer in the company — first line of code through to the Play Store listing — and built the app single-handed.
React NativeReduxRedux-Saga
iPhone & Apple Watch
iPhone & Apple Watch
iOS & Android
Datman, MetricStream and Talview own the products below. I own the engineering.
— Present
Bengaluru
Datman and Omnipay are Datman's payment products for restaurant owners and merchants. I built both from an empty repository in React Native, with Redux and Redux-Saga and a modular component system the second app inherited from the first. The architecture is built to carry over a million financial transactions a day, where data consistency under load isn't a nice-to-have.
Since then I've moved both apps onto Expo and Expo Router with OTA updates through Expo Updates, built the CI/CD pipeline that ships them — App Center and GitHub Actions, into both stores, without anyone touching a build machine — and added offline-first local storage, push notifications and the Reanimated work. Membership went from zero to 75,000+ over the same period, some of it on the back of performance and UX work I did.
—
Bengaluru
The MetricStream M7 mobile app: Android and iOS from one React Native codebase, for an enterprise governance, risk and compliance platform. I worked across the UI, Forms, CIM, CMP and REN modules, built the reusable component layer, and wrote the wrapper classes that kept third-party React Native libraries at arm's length — so replacing one didn't mean touching fifty files. I helped set up CI/CD and wrote the Jest suite.
—
Bengaluru
Where it started. Ember JS interfaces for Talview-Admin, on Ember, Semantic UI and hand-written HTML and CSS.
Every React Native CV says “integrated native modules”. This is what it meant on my side of it.
Datman needed card, wallet and bank-transfer payments inside two apps without either app ever touching card data. So the payment flows live in native code — Swift on iOS, Kotlin on Android — where the PCI-compliant paths and the platform’s own secure input already are. Tokenisation happens down there too, so what crosses the bridge back into JavaScript is a token and a status, and nothing else.
Above them sits one JS API: the same calls on both platforms, with results bridged back through TurboModules and Expo Modules rather than the event-emitter guesswork the old architecture forced on you. The point was never the native code. The point was that two app teams could take payments without either of them learning a platform payment SDK.
SwiftKotlinTurboModulesExpo ModulesNative tokenisationPCI-compliant payment flowsOne JS surface, two platforms
Listing tools proves nothing. Here's what each group is actually for, and the shipped app it went into.
since 2019
Six years and seven production apps. Expo Router for navigation, EAS Build for the pipeline and EAS Update for the fixes that can't wait for review, React Native Web where a screen also needed to be a page.
React NativeExpo RouterReact Native WebEAS Build & UpdateExpo NotificationsReanimated
Some things can't be done above the bridge — PCI payment flows, HealthKit, Screen Time. I write those in Swift and Kotlin and bring them back up through TurboModules or Expo Modules, or skip the bridge entirely and build the app native.
SwiftSwiftUIKotlinTurboModulesExpo Modules
Redux Toolkit with Redux-Saga where the async is genuinely complex and Persist where it has to survive a cold start; plain Context where a store would be ceremony. Offline-first means the app works on the train, so the local database is the source of truth and the network reconciles.
Redux ToolkitRedux-SagaRedux PersistReact ContextRealmAsyncStoragelocalforage
TypeScript end to end. React Hook Form paired with Zod, so one schema types the form and validates it instead of the two drifting apart. NativeWind so the styling vocabulary is the same on native and web.
TypeScriptReact Hook FormZodTailwindCSS / NativeWindGluestack UI
Enough backend to ship a product alone: Supabase for Postgres, Edge Functions and Storage, REST over Axios, Amplify where auth was already AWS, RevenueCat for subscriptions and the webhook that keeps entitlements honest, and the Claude API for the AI features.
SupabaseAxiosAWS Amplify (Auth)RevenueCatClaude APIPerfectCorp YouCam
GitHub Actions and App Center to both stores, Expo Updates for the fixes that can't wait for review, and instrumentation from day one — Sentry so I hear about a crash before a user reports it, Mixpanel and Clarity so retention is a measurement rather than an opinion.
GitHub ActionsApp CenterEASExpo UpdatesSentryMixpanelMicrosoft Clarity
Products I worked inside rather than owned. Here is exactly which part was mine.
Self-custodial crypto wallet
I built and maintained the entire user interface in TypeScript and React Native, with Context API for state — the save, send and spend flows for digital dollars, and the parts of a wallet UI where a wrong tap is unrecoverable.
TypeScriptReact NativeContext API
Cargo logistics
Live location detection and tracking, built on Mapbox with Redux and Saga, plus the UI around it. Tracking a truck is mostly a battery-versus-accuracy trade-off, and this one had to survive a driver's whole shift.
React NativeMapboxReduxRedux-Saga
I’m a mobile developer in Bengaluru. Six years on React Native, long enough to have shipped to both stores repeatedly and long enough to know when the answer isn’t in JavaScript.
What I’m best at is taking something from nothing. Most of the apps on this page started as an empty repository with me as the only engineer on them, and the ones that shipped are still in production with real users on them. Somewhere in there I picked up Swift and Kotlin, because a payment SDK and a Screen Time app can’t be written any other way.
At Datman I lead six developers. In practice that means code review, having the architecture argument early rather than after it’s expensive, and making sure the person who joined last month can find their way around by next week.
Email is the surest way. Everything else works too.
Anandkumar Patil — Senior React Native Developer, Bengaluru.