Most apps do not fail because the code was wrong. They fail because nobody decided what the app was for, so it ended up doing nine things badly. We start by cutting the idea down to the one thing it must do on day one, ship that properly, and add the rest once real people are using it.
Nexgino has been building software since 2023, from our office in Kolkata, for clients across India and abroad. Our work is on phones across the country — a national esports streaming platform, a pharmacy distribution app used daily by retailers, a crypto mining app with over a million installs. That is the standard we build to, whether the app is for twelve users or twelve lakh.
What we build
Every app below is something we have shipped, not a category from a brochure.
Marketplace and ordering apps
A catalogue, a cart, payments, order tracking and a seller side that actually works. The hard part is never the checkout — it is what happens when an order is cancelled halfway, or a payment succeeds but the order does not. We build those paths first.
Booking and appointment apps
Slots, availability, reminders, rescheduling and refunds. Clinics, salons, coaching centres, service teams. The rule we follow: a customer should never see a slot that has already gone.
Delivery and live tracking apps
Rider apps, dispatch screens, live location on a map and status that updates without a refresh. This is where most agencies quietly give up, because the battery and network behaviour on a real Indian phone on a real Indian road is nothing like the emulator.
B2B and internal apps
Field sales, stock, attendance, distributor ordering. Fewer users, higher stakes — if it breaks, somebody's day stops. These get the strictest offline handling and the clearest error messages.
Content and community apps
Feeds, profiles, uploads, chat, notifications. Built so the feed stays fast at ten thousand items, not just at ten.
What we build it with
Flutter
One codebase, both platforms, a single team. For most apps this is the right answer — it is faster to build, cheaper to maintain, and the result is indistinguishable from native to the person holding the phone.
React Native
When you already have a React team, or a web product you want to share logic with.
Native Swift and Kotlin
When the app leans hard on the camera, Bluetooth, background location or platform features that cross-platform tooling handles badly. We will tell you when this is the case rather than pretend Flutter covers everything.
The backend
PHP or Node, a proper relational database, APIs that are versioned and documented. Hosting on whatever you can actually afford to run for three years, not whatever is fashionable.
How an app project runs
Scope
A call, then a written scope with screens listed and a fixed price against them. If we cannot describe a screen, it is not in the scope. This is where most disputes are prevented.
Design
Screens designed and shown to you before a line of app code is written. Changing a screen in design costs an hour. Changing it after it is built costs a week.
Build
Built in stages you can open on your own phone. You see progress every week, not a black box for two months followed by a reveal.
Test
On real devices, on a real network, including the cheap Android phone your customers actually use. Payments tested with real money moving in test mode, then live.
Launch
We handle the Play Store and App Store submission, the listing, the screenshots and the review process. Rejections happen; we deal with them.
After
Support after launch is part of the agreement, not a surprise invoice. Crashes are our problem, not yours.
What decides the cost
We do not publish a price list, because an app is not a product on a shelf. What we can do is tell you honestly what moves the number, so you can judge any quote — ours or anyone else's.
How many screens
The single biggest factor. Fifteen screens is a different project from fifty.
Whether money moves through it
Payments, refunds, wallets and settlements add work everywhere — not just at checkout, but in every failure path around it.
Whether it is live
Live tracking, chat and real-time updates need infrastructure that idle apps do not.
How many kinds of user
A customer app is one app. A customer app plus a rider app plus an admin panel is three.
Whether it needs an admin panel
Almost every app does, and it is frequently forgotten in cheap quotes. Then you find you cannot change a price without calling the developer.
Who owns it afterwards
We hand over the code and the accounts. Some quotes are cheaper because they do not.
Apps we have worked on
RetailerShakti
A B2B platform for pharmaceutical and wellness distribution, used daily by retail pharmacies.
Read the case studyFlipkart Health+
The health and pharmacy arm of the Flipkart Group, delivering medicines and wellness products.
Read the case studySastaSundar
One of India's established online pharmacy and digital healthcare platforms.
Read the case studySai Crop Science
A crop-protection company reaching farmers across the country.
Read the case studyWho this is for
A good fit
- You have a business that already works and you want an app that makes it work better.
- You have tried a cheap developer once and got something that half worked.
- You need the person building it to tell you when your idea has a problem.
- You want to own the code and the accounts at the end of it.
Probably not a fit
- You want the cheapest possible quote and nothing else matters.
- You need it live in two weeks and the scope is still changing.
- You want us to build a clone of an existing app and are not sure why.
Questions we get asked
How much does it cost to make an app in India?
It depends almost entirely on the number of screens and whether money moves through the app. A simple catalogue app is a fraction of the cost of a marketplace with payments, live tracking and three types of user. We scope the screens first and quote a fixed price against that list, so you are not agreeing to a number before anyone knows what is being built.
How long does it take to build a mobile app?
A focused first version is usually a few months from scope to store. What lengthens it is not the code — it is unfinished decisions. Projects that run late almost always ran late because the scope kept moving, not because the build was slow.
Should I build for Android first or both together?
In India, Android first is often the sensible answer if budget is tight, because that is where your users are. With Flutter, building both together costs far less than twice one, so most projects do both from the start.
Do I own the code?
Yes. The code, the repository and the store accounts are yours, handed over at the end. We will not hold your project hostage, and you should be wary of anyone who structures it otherwise.
Do you work with clients across India?
Most of our work is with clients in other cities and abroad. The whole project runs over calls, written scope and shared access, so where you are makes no difference to how it is built. Being based in Kolkata rather than Bangalore or Gurgaon keeps our costs lower, which is your advantage.
What happens after the app is live?
Support is written into the agreement. Crashes and bugs in what we built are fixed as part of it. New features are quoted separately, because they are new work.
The other things we do
Tell us what the app needs to do.
A call, then a written scope with a fixed price. No obligation, and no sales pitch.
Start a project