NM Company
A portfolio and enquiry site for events firm NM Company
A visual portfolio and enquiry website for an event management and supplies firm — presenting a full...
Read itiOS, Android and cross-platform
Mobile App Development
Flutter, React Native and native apps that hold up offline, on old hardware and on a metro platform with one bar of signal — shipped to both stores with a release pipeline you own.
- Offline-first sync with durable write queues and a defined conflict rule
- Cold start under 2 seconds on a 3GB Android device
- Automated builds to TestFlight and the Play Console on every merge
- Crash-free sessions above 99.5% before we call it launched
What this is
Built for the phone your customer actually owns.
An app is not a website in a frame. It is a piece of software that has to work on a five-year-old Redmi with 3GB of RAM, on the Delhi Metro where the network drops between Rajiv Chowk and Barakhamba, and on a device where the user has already decided — in about eight seconds — whether to keep it or uninstall it.
We build mobile products for teams who have a real reason to be on the home screen: a delivery fleet that works offline, a field-service workflow with a camera and a signature, a members app where push is the primary channel, a fintech flow that has to survive an RBI audit. If your users would be equally happy with a good mobile site, we will tell you that and save you a year of app-store maintenance.
Cross-platform by default, native when the hardware demands it. Flutter and React Native cover the overwhelming majority of what people ask us for, and they cover it with one codebase, one release train and one set of tests. When you need Bluetooth Low Energy, an SDK that only ships for iOS, background location that has to survive Doze mode, or 120fps rendering, we write native modules — or the whole thing in Swift and Kotlin — and we say so before you sign.
- Cross-platform first — native modules only where the hardware demands it
- Offline-first architecture, not an afterthought bolted on in month five
- Store submission, signing and release automation handed over to you
The first decision
Flutter, React Native or native — honestly.
| Flutter | React Native | Native (Swift / Kotlin) | |
|---|---|---|---|
| One codebase, both stores | Yes | Yes | No |
| Performance on 3GB Android | Excellent | Good | Excellent |
| Custom, brand-heavy interfaces | Excellent | Good | Excellent |
| Shares code with a React web app | No | Yes | No |
| Deep hardware and BLE work | Via native modules | Via native modules | Native |
| Hiring pool in India | Large and growing | Very large | Smaller, pricier |
| Typical cost vs native | ~60% | ~65% | Baseline |
Where apps break
The failures we are hired to fix.
Almost every rescue we take on fails in one of these six places. None of them are visible in a Figma file.
-
It dies the moment the signal does
The delivery partner walks into a basement and the app shows a spinner until the OS kills it. Twenty minutes of proof-of-delivery photos gone.
-
Nine-second cold start
Every SDK the marketing team ever asked for initialises on the main thread before the first frame paints. Users uninstall before they see your logo.
-
Crash-free rate below 97%
Nobody wired up Crashlytics or Sentry, so the crashes are invisible. Your Play Store rating is dropping and no one can say why.
-
Payments fail silently
UPI intent bounces back to the app with no callback, the order is charged but never confirmed, and support reconciles refunds by hand every morning.
-
The keystore is on somebody's laptop
The previous agency has the signing key. You cannot ship an update to your own Android app without their goodwill.
-
Push notifications reach half the users
No topic strategy, no token refresh handling, Chinese OEM battery optimisers killing the service. Your only re-engagement channel is leaking.
How we build
From idea to both stores.
You are in a TestFlight build by week six. Not staring at a Gantt chart.
-
01
Product shaping and platform call
1–2 weeksWe map the core job the app does, the device profiles it must survive, and the connectivity it will actually see. We choose Flutter, React Native or native — and we write down why, including what we are giving up. You get a scope, a device test matrix and a number.
-
02
Interaction design and prototype
2–3 weeksNative platform conventions, not a web layout squeezed into a phone. Gestures, transitions, the offline and error states, the permissions priming screens. We put a clickable prototype in front of five real users from your segment before we build it.
-
03
Backend and sync engine
3–5 weeksThe API, the auth, the push infrastructure and the sync protocol — usually the 40% of the work that other quotes forget. Durable local storage, a write queue that survives an app kill, and a conflict-resolution rule we agree with you explicitly.
-
04
App build in two-week increments
6–12 weeksEvery merge produces a signed build in TestFlight and the Play internal track. You install it on your own phone the same day. Widget and integration tests run in CI; the low-end device sits on a desk here and gets tested on manually every sprint.
-
05
Store submission and launch
2–3 weeksListings, screenshots, privacy labels, the data-safety form, account-deletion flow, and the review cycle including the rejections. Staged rollout on Android — 5%, 20%, 100% — with the crash dashboard open the whole way.
-
06
Post-launch tuning
30 days, then ongoingWe watch crash-free sessions, ANR rate, cold start and funnel drop-off on real traffic. Defects fixed at no charge. Then we hand over the pipeline and the keys — or stay on for the roadmap.
Offline-first
The lift has no signal. The app should not care.
Offline is where most Indian apps quietly fall apart. A form that loses twenty minutes of a field agent's work because the lift had no signal is not a UX inconvenience — it is the reason the agent goes back to paper.
We treat the local database as the source of truth for the session and the server as the thing you eventually reconcile with. Writes queue durably on device. Conflicts resolve against a rule we agree with you in discovery — last-write-wins, server-authoritative, or a merge with a human in the loop — rather than whatever the sync library happened to do. Uploads resume after the app is killed. The user sees what is pending, what has synced and what failed, because silence is worse than a bad number.
What you get
Everything a shipped app needs.
A release pipeline you own
Fastlane lanes for signing, versioning and upload. Every merge to main produces a build in TestFlight and the Play internal track, tagged and traceable back to a commit. Your team can ship without us on day one — and without us on day four hundred.
Push that actually arrives
FCM and APNs with token refresh, topic segmentation, deep links into the right screen, and workarounds for the OEM battery optimisers that silently kill background services on Xiaomi, Oppo and Vivo handsets.
Payments that reconcile
Razorpay, PhonePe or Cashfree with UPI intent, cards and netbanking — plus server-side webhook verification so a charged-but-unconfirmed order is impossible, not just unlikely.
Crash and performance telemetry
Sentry or Crashlytics with source maps, ANR tracking, cold-start traces and a funnel dashboard. You will know about a bad release from a graph, not from a one-star review.
A device matrix, not a MacBook simulator
We keep a low-end Android with 3GB of RAM, a mid-range Samsung and an older iPhone on the desk. Cold start, jank and memory are measured on those, because that is what your customer is holding. A screen that drops frames on the cheap phone does not ship.
The stack
What we reach for.
Chosen for device reality and for your ability to hire against it later.
Flutter
Dart
React Native
TypeScript
Swift / SwiftUI
Kotlin / Compose
SQLite / Drift
WatermelonDB
Riverpod
Firebase
Laravel API
Fastlane
FCM / APNs
Razorpay SDK
Sentry
Firebase Analytics
Maps SDK
Our release bar
Numbers we will not launch below.
These are release gates, not aspirations. If a build misses one of them on the low-end device in our test matrix, it does not go to the store — regardless of what the calendar says. Holding the line here is why our apps do not arrive at a one-star average in week two.
Talk about your app
0%
Crash-free sessions
Measured across the device matrix
0s
Cold start
3GB RAM Android, cold cache
0MB
Median download size
Android app bundle, split per ABI
0fps
Scroll performance
No dropped frames on core screens
Proof
All case studies
Apps in daily use.
Field teams, delivery fleets and consumer products that survive real Indian network conditions.
01
FealDeal — E-commerce — Ethnic Fashion
A high-catalogue ethnic-wear storefront for FealDeal
A Shopify storefront for a Surat ethnic-wear label — 200+ SKUs of lehengas, sarees and suits organised by type, colour,...
Shopify
Platform
0+ SKUs
Catalogue
Mobile-first
Storefront
02
Turant Logistics — Logistics & Supply Chain
Cutting order-to-dispatch by 62% for a 400-truck 3PL
A fleet, ePOD and route-optimisation platform built offline-first for drivers in low-connectivity corridors — because th...
0% faster
Faster order-to-dispatch on the ops floor
0% shorter
Shorter POD-to-invoice cycle (8.4 days to 19 hours)
0% lower
Fewer empty-run kilometres in the first full quarter
03
Collection by Rehan — E-commerce — Watches & Accessories
A brand-led watch and eyewear store for Collection by Rehan
A Shopify storefront for a Surat watch and eyewear retailer — browsable by gender, brand, style and combo, with predicti...
Shopify
Platform
Brand & style
Browse by
COD-ready
Checkout
Flutter when the interface is bespoke and you want pixel-identical rendering on both platforms with the best low-end performance. React Native when you already have a React web team and want to share logic and hiring. Native when the app lives close to the hardware — BLE peripherals, ARKit, background location that must survive Doze, or a vendor SDK that only ships for one platform. We recommend, we justify it in writing, and you decide.
Yes, and we build the pipeline so you can do it without us later. That means Fastlane lanes for signing and upload, automated builds to TestFlight and the Play internal track on every merge to main, store listings with screenshots, privacy nutrition labels, and the data-safety form. We also handle the rejections, which happen: account deletion flows, permission justifications and payment-policy questions are the usual culprits.
For physical goods and services in India we integrate Razorpay, PhonePe or Cashfree with UPI intent, cards, netbanking and wallets, plus UPI Autopay for subscriptions. For digital content Apple and Google require their own in-app purchase rails and take their cut — we implement StoreKit 2 and Play Billing with server-side receipt validation. We will tell you plainly which category your product falls into before it becomes a rejection.
We buy the phones. Our test matrix includes a low-end Android with 3GB of RAM and an older iPhone SE, not just flagships. We profile cold start, jank frames and memory on those devices, budget the app bundle size, defer everything non-essential off the startup path, and lazy-load images at the resolution the screen actually needs. If a screen drops frames on the cheap device, it is a bug and it blocks release.
A single-role app with auth, a core workflow, push and payments is typically 12 to 16 weeks and lands in the ₹8L to ₹18L range. A multi-role platform — customer app, partner app, admin console, offline sync, live tracking — runs 20 to 30 weeks and prices accordingly. The backend is usually about 40% of the work, which is the part most quotes quietly leave out. Ours does not.
You do. The Apple Developer and Google Play accounts are registered in your company name with your billing, and the signing certificates and keystores are handed to you in a vault you control. We have inherited too many projects where the previous agency held the keystore hostage. It will not happen here — you can revoke our access on any day of the engagement and still ship an update.
Show us the workflow that breaks when the signal drops.
Bring the field process, the device your users actually hold, and the constraint everyone else told you was impossible. We will tell you what it takes.
Proof
Shipped, measured, still running.
Swasthya Sarathi
A healthcare-companion platform for Swasthya Sarathi
A multi-service healthcare platform that helps people find hospitals, doctors, labs, medical stores,...
Read itMV Tech Education
A course and admissions platform for MV Tech Education
A course-catalogue and admissions website for a Bihar vocational institute — leading with industrial...
Read itRelated services
Web Development
Production web applications built on Laravel, Next.js and Postgres — typed, tested, observ...
ExploreEcommerce Development
Commerce platforms where the checkout converts and the back office reconciles — multi-ware...
ExploreERP Development
ERP systems built on an append-only stock and financial ledger — multi-plant, multi-GSTIN,...
ExploreLet's talk mobile app development
Bring us the hard version of the problem.
A senior engineer reads every enquiry. You'll get a real answer — scope, risk and a number — within one business day.