We design and build Android and iOS apps from our office in Sitapaila, Kathmandu. That includes the backend behind the app, the payment and SMS integrations Nepali users expect, the Play Store and App Store submissions, and the support after launch.
Most app projects that go wrong in Nepal go wrong for the same reason. Someone quotes for "the app", builds the screens, and then discovers the app needs a server, a database, an admin panel for the office staff, a payment gateway that actually settles into a Nepali bank account, and an SMS provider for OTP. Those get bolted on late, by whoever is cheapest that week, and the client ends up with something nobody wants to maintain.
We quote the whole thing from the start. Our Laravel team builds the backend and the admin panel, our Flutter and native developers build the app, and one project manager sits across both. When you call us in month eight because a payment failed, the person answering can see the whole system.
Four kinds of app work, each with its own team. Most clients need the first one and part of the fourth.
One codebase, two stores. This is what we recommend for most business apps in Nepal, because it gets you iOS for a fraction of the cost of building it twice.
Our Flutter teamKotlin for Android, Swift for iOS. Worth it when the app leans hard on the hardware, needs the best possible performance, or has to pass a bank's security review.
The server side in Laravel, with an admin panel your staff will actually use. This is the half of the project other quotes tend to leave out.
Our Laravel teamOS updates, store policy changes, expired certificates, a payment gateway that changed its API. We keep apps alive, including ones we did not build.
These are the briefs that come through our door in Kathmandu week after week. If yours is not here, that is fine; the list is what we have seen, not what we can do.
Five stages. You sign off at the end of each, and the price does not change unless the scope does.
A working session at our office or yours, usually two to three hours. We map the screens, the user roles, the integrations and the admin side, then write it up as a scope document with a fixed price and timeline. You keep the document whether or not you proceed.
Every screen designed in Figma before a line of code. You click through a working prototype on your own phone and change anything you like at this stage, because changing it later costs ten times more.
Two-week sprints. At the end of each you get a test build on your phone through TestFlight and Google Play internal testing, plus a short note on what changed. The backend and admin panel are built in parallel by the Laravel team.
We test on real low-end and high-end Android devices and current iPhones, not just simulators. Then we prepare the listings, screenshots, privacy policy and data-safety forms, and submit. Apple developer enrolment for a Nepali company needs a D-U-N-S number and a dollar card; we walk you through both.
Ninety days of bug fixing is included with every project. After that, a monthly maintenance plan covers OS updates, store policy changes, certificate renewals and small improvements. Most clients stay on it.
The things an overseas agency will not know about and a first-time developer will underestimate. We have done each of them enough times to quote them accurately.
Boring, well-supported choices on purpose. Every one of these will still have developers available in Nepal in five years.
Office: Sitapaila, Kathmandu. You are welcome to visit before you sign anything.
If yours is not here, ask us on WhatsApp. Someone technical answers, not a sales script.
At Web House Nepal a simple business app for Android and iOS starts from around NPR 3,50,000. An app with its own backend, admin panel, payments and OTP login usually lands between NPR 8,00,000 and NPR 20,00,000. Anything involving banking compliance, offline sync or ERP integration is quoted after a scoping session.
The three things that move the price most are the number of screens, how much backend logic sits behind them, and how many outside systems the app has to talk to. A quote that does not ask you about all three is a guess.
A starter app takes six to eight weeks from signed scope to store submission. A business app with a backend takes ten to fourteen weeks. Apple's review adds a few days at the end, and Google Play can take up to a week to approve a brand-new developer account, so we get that started in week one.
In Nepal, Android is well over ninety percent of the market. If budget forces a choice, Android first. For most clients we recommend Flutter, which produces both apps from one codebase, so iOS comes for a small additional cost rather than as a second project.
You do. The Play Console and App Store Connect accounts are created in your company's name, the source code lives in a repository you control, and the backend runs on hosting in your name. If you ever move to another developer, nothing is locked with us.
Yes. We have integrated eSewa, Khalti, IME Pay, ConnectIPS and Fonepay QR in both apps and websites. We also handle SMS OTP through Nepali providers, Bikram Sambat dates, and Nepali Unicode input.
Usually. We start with a paid code audit so both sides know what state it is in before committing. If the previous developer will not hand over the source or the store accounts, we can advise on rebuilding, which is sometimes cheaper than untangling.
Yes, before the scoping session if you want one. We have a standard mutual NDA, or we will sign yours.
Small changes are covered by the maintenance plan. Larger features get scoped and quoted separately, the same way the original project was. You are never obliged to use us for them, because you own the code.
Send a paragraph, a sketch, or a competitor's app you like. We will come back within one working day with questions, and a scoping session if it makes sense.