What decides the cost of a mobile app in Malaysia

The short answer

The cost of a mobile app in Malaysia depends on five things: the number of screens, whether it runs on both phone platforms, features such as accounts, payments or chat, how much runs on a server behind it, and care after launch. A good developer turns those into a written scope with one fixed price first.

The drivers, one by one

Screens and user journeys

Count what users must do, not just screens. Signing up, booking, paying and checking a history are each a journey of several screens. Every screen needs a design, empty and error states, and testing on real phones. An app for your own staff often needs fewer screens than one for the public. Name the three journeys that matter most and build those first.

Phone platforms and a web version

Most businesses in Malaysia need both major phone platforms, because their customers use both. Each platform has its own rules, its own store and its own review before release. Some projects also need a web version that opens in a browser. Each extra platform adds testing and release work. Ask which platforms the quote covers and how they are built.

Languages

If your customers read English, Chinese or Malay, the app may need more than one language. Each one adds text to every screen, store listings in that language, and a check that longer words still fit their buttons. An app can also follow the phone's language setting. Decide which languages you need at launch, and ask for them to be named in the scope.

Features: accounts, payments, chat and notifications

Features move the cost more than anything else. Accounts need secure sign-in and a way to recover a lost login. Payments need checkout, refunds and receipts. Chat needs messages that arrive instantly and in order. Notifications must reach the phone when the app is closed. Bookings, maps, uploads and payouts each add rules. Mark what you need at launch and get only that quoted.

The server and admin console behind the app

Most apps are only the front of the work. Behind them sits a server that stores accounts, orders and messages, sends notifications and runs scheduled tasks. Your team also needs a console to see users, handle refunds and change content without a new release. This part grows with everything the app does. Ask what the server does and who hosts it.

Content and design level

An app needs words, images and icons on every screen, plus store listings with screenshots. If you supply them, the work is mostly design and build. If the developer writes or draws them, that belongs in the quote. Design runs from a clean layout in your brand colours to original illustration and motion. Custom art takes more design rounds and more testing.

Integrations and data

An integration connects your app to another service: a payment provider, a delivery partner, a map, a text-message service for sign-in codes or an accounting tool. Each one needs set-up, testing and a plan for when that service changes. Importing existing customers is its own task. List the systems you already use, so the developer can quote the connections up front.

Store listings, releases and care after launch

An app is never finished at launch. Each store reviews the app before it goes live and may ask for changes. New versions of the phone systems arrive regularly, and an app that is not updated can stop working properly. Users also report bugs and ask for features. Ask who handles the store review, how updates are quoted, and who you contact when something breaks.

What is usually included in a fixed quote

• A written scope listing every screen, platform, language and feature.
• One price for that scope, approved before work starts.
• Designs revised on your phone until you approve them.
• The app for each platform in scope, with its server and console.
• Testing on real phones, plus test versions you can install.
• Store listings submitted, and everything handed over in your name.

What is usually not included, and how it is handled

• Anything outside the agreed scope. It is quoted first, and you decide before it is done.
• New features and phone system updates after launch. These are quoted before they start.
• Third-party running costs. You pay for store accounts, hosting, messaging and payment processing in your own name, so they stay yours.
• Writing, illustration and photography. These are in the quote only when the scope says so.

Recurring costs to expect

• App store accounts. One developer account per store, one renewed yearly and one paid once.
• Server hosting. Keeps accounts, orders and messages online.
• Domain and email. For the app's website and support address.
• Payment processing fees. The provider keeps a share of each payment.
• Store commission. The store usually takes a share of digital items sold in the app.
• Messaging services. Text-message codes and some notifications are charged per use.

How to compare quotes

1. Which screens, platforms and features are in the scope? 2. Is this one fixed price, and what happens if I ask for something outside it? 3. Are the store accounts, the server and the source files in my name from the start? 4. Which running costs will I pay after launch? 5. Can I install a test version on my own phone before release? 6. How are fixes and phone system updates handled after launch?