On almost every first call we get from a Malaysian SME, somewhere in the first ten minutes, the founder says it: 'we want to build an app'. Sometimes they have a sketch. Sometimes they have a Figma file from a previous quote. Sometimes it's just a feeling that the business needs one. The conversation that follows is usually the same. We ask what the app should do, they describe a list of features, and within fifteen minutes we've quietly worked out together that what they actually need is a faster website with a WhatsApp button and a clean checkout. Not an app.
This article is the long version of that conversation. We do build mobile apps. We charge between RM40,000 and RM200,000 for them, and we run a real React Native and native iOS practice. We also turn down more app projects than we accept, because for the average Malaysian SME in 2026, a native mobile app is the wrong tool for the wrong problem at the wrong cost. The good news: in most cases there's a better answer that costs a fraction of the price and converts more customers.
What a mobile app actually costs in Malaysia
Forget the 'I have a friend who knows a developer in Cyberjaya' quotes. A real, shippable mobile app built by a Malaysian studio in 2026 sits in this range, and the bands are remarkably stable across the local market:
- RM25,000 to RM50,000 for a single-platform MVP, typically Android first because of the user base in Malaysia, or iOS first if the audience is B2B premium. React Native or Flutter, a handful of screens, basic backend, no App Store optimisation bundled.
- RM50,000 to RM100,000 for a proper cross-platform build covering both Android and iOS, with a real backend, push notifications wired correctly, payment integration via iPay88 or Stripe, and a CMS so non-technical staff can update content without a developer.
- RM100,000 to RM250,000 for a complex production app: real-time features, offline sync, multiple user roles, accounting or inventory integration with SQL Account or AutoCount, custom hardware support, App Store and Play Store optimisation done properly, and the engine room behind it.
Those numbers buy you version 1. Version 1 is not where the cost stops, and this is the part that breaks most Malaysian SME app dreams. The maintenance burden after launch is roughly 20% to 30% of the build cost per year, every year, forever. App Store and Play Store policies change. iOS and Android push out major updates that quietly break things. Your push notification provider deprecates an API. Your backend hosting bill creeps up. A user leaves a one-star review because the app crashes on their five-year-old Samsung A21s and now the algorithm deprioritises you. None of this is hypothetical. It's the spreadsheet we share with every prospective client before they sign.
The one question we ask before anyone signs a contract
There's a single question that separates 'this client should build an app' from 'this client should build a better website'. We ask it in some form on every discovery call. The question is: how often do you need to be on the user's home screen? Not how often does the user want your service. Not how often do they visit your site. How often do you, as the business, need to be one tap away on their phone, with permission to push a notification into their lock screen, with their stored login already inside?
If the answer is 'every day' or 'every other day', an app might make sense. If the answer is 'once every few months when they need our service', it doesn't, no matter what your competitors are doing. The home screen is the most expensive real estate in mobile computing. Earning a spot there costs the user a deliberate install action, an OS permission dance, and ongoing storage they will eventually reclaim. A website asks for none of that. It loads when needed, disappears when not, and the same user can find you again three months later via Google without remembering your brand name.
The PWA: 80% of the app, 20% of the cost
Progressive Web Apps are the most underused tool in the Malaysian SME stack right now. A PWA is a regular website built to behave like an app on a phone. It can be 'installed' to the home screen from the browser. It can send push notifications, yes, even on iOS as of 2024. It can work offline. It can access the camera, microphone, and GPS. It loads instantly because it's already been served and cached. It costs roughly the same as a normal modern website to build, because it is a normal modern website with three or four extra technical layers stitched in.
We've shipped PWAs for Malaysian F&B chains, professional services firms, and a logistics startup last quarter. The conversion rate on 'do you want to install this on your home screen' is typically 5% to 15% of returning visitors, which is roughly the same ballpark as the install rate for a native app from a Play Store listing. Except there's no App Store approval, no 30% Apple tax on in-app purchases, no version submission cycle, and no parallel codebase to maintain. For about 80% of the SME briefs that walk through our door asking for a mobile app, a PWA does the job. The remaining 20% genuinely need native, and we'll happily build that for them.
The 4 times a real native app actually makes sense
This is the checklist we share with every client who insists they need a native build. If you can honestly tick at least two of the four, native is probably the right answer. If you tick zero or one, walk away from the app brief and put the budget into a better website with a PWA layer. You will get more customers for less money. We will tell you the same thing on the call.
One: push notifications are core to the business model, not a nice-to-have. The user genuinely benefits from being interrupted. A food delivery rider needs the order ping. A financial trading app needs the price alert. A queue management app needs the 'you're next in line' notification. If push is just 'we want to remind people about promotions', that's not core, that's spam waiting to happen, and the user has been trained to disable promotional notifications within a week of install.
Two: offline functionality is required because the user is genuinely offline for meaningful stretches of time. Field inspectors at oil and gas sites in Terengganu. Estate workers in deep palm-oil plantations in Sabah. Sales teams on the East Coast with patchy 4G. Tourists in Borneo where data roaming dies. If 'offline' means 'their Wi-Fi was slow for ten seconds', a fast website handles that better than any app does, because the user simply waits a second longer.
Three: native device capabilities are core to the value proposition, not decoration. AR try-on for an eyewear or furniture brand. Camera-driven document scanning for a financial onboarding flow. Biometric authentication for a banking-grade product. Background GPS tracking for a logistics app. Bluetooth pairing for a hardware product. These are real native features that browsers cannot replicate with the same quality, and if they're the reason the user opens the app at all, you need native code.
Four: you have, or can credibly project, a large enough active audience to justify the install friction. The Malaysian benchmark we use: if you can't see yourself with at least 5,000 monthly active users within 12 months of launch, the app is going to feel empty, ratings will suffer, the algorithm will deprioritise you in the stores, and the per-user cost of the build will be unbearable. Below that scale, a website serves more humans for less money. Above it, app economics start to work in your favour.
What we usually build for clients who came in asking for an app
Here's the rough shape of where these conversations land, sorted by the original brief the founder walked in with. The pattern is consistent enough that we can almost predict the redirect before the discovery call ends.
- F&B brand wants 'a delivery app like Foodpanda but for our own restaurant chain'. We usually build: a fast mobile-first website with menu, branch finder, WhatsApp ordering deep-links, table reservations, and a PWA install prompt. Cost: RM18,000 to RM30,000 instead of RM120,000. Result: more orders, same brand reach, no Play Store reviews to manage.
- Professional services firm wants 'a client portal app for our customers to track their case'. We usually build: a clean web app on a secure subdomain, mobile responsive, login with email or phone OTP, document upload, status tracking, PWA-installable for repeat clients. Cost: RM25,000 to RM45,000 instead of RM150,000. Result: faster shipping, easier to hire a developer to maintain it because it's standard web tech.
- Retail brand wants 'a loyalty app where customers collect points'. We usually build: a WhatsApp Business API integration with a simple web dashboard, or a PWA loyalty page tied to phone number with passkey login. Cost: under RM20,000 versus RM80,000 for a native loyalty app. Result: an actually-used loyalty programme instead of an abandoned install.
- Genuine app brief: a Malaysian logistics startup needed real-time driver tracking, offline route caching, native Google Maps integration, and push notifications to drivers in remote zones. That's a real native build, not a website pretending to be one. Cost: RM180,000. Result: actually used by 800 drivers daily, with sub-2-second response times in production.
The decision framework, on one screen
If you're a Malaysian SME founder reading this on your phone and you're not sure which side of the line you fall on, here's the shortest possible version. Ask yourself, honestly, with the answers a future-you would give rather than the founder fantasy version:
- Does your user need you on their home screen, with push permission, more than once a week? If no: website or PWA.
- Does your product genuinely need native device capabilities like AR, biometrics, background GPS, or hardware pairing? If no: website or PWA.
- Will your user be offline for meaningful periods while still needing your product? If no: website or PWA.
- Can you realistically reach 5,000 monthly active users within 12 months? If no: website or PWA.
Three or four 'no' answers means an app is almost certainly the wrong investment for your business in 2026. One 'yes' answer is not a green light either, it's a signal to consider. Two or three 'yes' answers and we'd seriously consider native. Four 'yes' answers and you have a real app project, and you should budget RM50,000 minimum to do it properly, plus the annual maintenance line.
What the wrong choice actually costs
We've watched this failure mode play out enough times to describe it from memory. The SME pays RM60,000 for a basic native app. It launches with reasonable fanfare on the company Instagram. Installs trickle in for the first month, mostly from staff and friends. By month three, the active user count is 200 and most of those are family. By month six, an iOS update breaks the build, the original developer is on a new project, and the founder is paying a freelancer RM5,000 to patch it. By month twelve, the app is functionally abandoned but still in the stores, collecting one-star reviews from users whose accounts no longer work. The website, meanwhile, has been ignored because all the energy went into the app. Compounding loss on two surfaces at once.
The right version of the same story: the SME spends RM25,000 on a mobile-first website with a PWA install prompt, WhatsApp deep-linking, and a fast checkout flow. By month six the site is the primary inbound channel, the team has learned what messaging actually converts, and they've banked RM35,000 of the original app budget. That RM35,000 either goes into paid acquisition that the new site can absorb properly, or it stays in the bank. Both are better outcomes than the app-shaped hole.
When you actually do come to us for an app
If your situation genuinely lands on the native-app side of the decision, here's roughly what the engagement looks like. Discovery week, same shape as a website project. Then a two-week design phase, where we design two screens to completion and a small design system that the rest of the app inherits from. Then six to eight weeks of build using React Native for genuinely cross-platform briefs, or native Kotlin or Swift for performance-critical builds. Staging via TestFlight and Play Store internal testing. App Store and Play Store submission with screenshots, copy, and metadata done properly, not as a launch-week afterthought. Total: roughly 10 to 12 weeks from kickoff to live in both stores.
We also tell clients on day one what the ongoing cost looks like, because most studios don't. Plan for at least RM800 a month in hosting and third-party services (push notifications, crash reporting, analytics). Plan for RM5,000 to RM15,000 a quarter in maintenance, depending on the complexity of the backend. Plan for one minor update per quarter and one major update per year. If you can't accommodate that operating cost, the app will be dead within 18 months regardless of how well it was built. That's not a studio failure, it's an operating math failure that no agency can save you from.
The honest summary
Most Malaysian SMEs who walk in asking for a mobile app would be better served by a fast mobile-first website with a PWA layer and a properly integrated WhatsApp flow. The cases that genuinely warrant a native build are the ones where push, offline, native capabilities, or scale make the install friction worth paying. If your project doesn't clear those bars, the kindest thing a studio can do is talk you out of it, and we will. Talking founders out of bad app builds is, surprisingly often, the most useful conversation we have all week.
If you'd like a frank conversation about which side of the line your business falls on, we offer free 30-minute calls over Google Meet. No pitch, no slides, just an honest read of your situation and the cheapest credible recommendation, whether that's a website, a PWA, or a real native app.
