Mobile App Development in Malaysia. For enterprises and institutions.
Last updated: November 2026
shakalakaa builds native iOS and Android or cross-platform apps for Malaysian organisations with a real operational use: field teams, member and patient apps, booking and loyalty.
Each project is scoped and quoted on its own, with no fixed price. Every app, including progressive web apps (PWAs), is integrated with the CRM, WhatsApp and back-end systems the organisation already runs.
Trusted by Malaysian GLCs, listed groups and platforms
Apps with an operational job to do
An app earns its place when it removes a step someone does by hand every day. These are the four kinds we build.
Operational apps
Carrier, field-team and driver apps that record jobs, photos and sign-offs where the work happens.
Customer apps
Booking, membership and loyalty apps for groups with many branches or departments.
Internal tools
Approval, inspection and reporting tools for staff who are rarely at a desk.
App, CRM and WhatsApp together
The app shares its data with the CRM and the WhatsApp flows, so a booking made in one shows in the others. See custom software.
We build management systems, booking systems, portals, progressive web apps (PWAs) and native or cross-platform iOS and Android apps for large organisations, including carrier and driver apps for operational teams.
By industry
What we build for each sector is set out on its industry page:
- Aesthetic clinic marketing
- B2B marketing
- Beauty and wellness brand marketing
- Dental clinic marketing
- E-commerce marketing
- Education marketing
- F&B and restaurant marketing
- Healthcare and hospital marketing
- Interior design marketing
- Loan marketing
- Property marketing
- Travel and hotel marketing
- Marketing for large brands
Service timeline
Discovery
Document how the workflow runs today, including the workarounds, before designing what replaces them.
UX
Screens and flows designed around the people who will use the app every day, and tested with them.
Build & Integration
Development wired into your existing systems, such as the CRM, booking and WhatsApp, rather than replacing them.
Store release
The app is prepared and submitted for release on the App Store and Google Play.
Support Window
Post-launch support catches real-world issues; ongoing maintenance continues on retainer after that if you want it.
Native, cross-platform or PWA: which your app should be
For groups, chains and institutions whose app runs a daily operation, the build type decides cost of upkeep, reach and what the app can touch on the phone.
After launch: stores, ownership and upkeep
Native and cross-platform apps are published under your own Apple and Google developer accounts, so the listing, the reviews and the users stay yours.
At handover you receive the source code, the database and hosting access, as set out in the ownership answer below.
Phones change every year. Upkeep covers new iOS and Android versions, store policy changes, security fixes and the small changes staff ask for once they use the app daily.
What we have built
Plixitt LMS is the lead-management system we specified, built and run for our own enquiries.
It is not a product we sell. It is the kind of back end an app plugs into.
We built and run a Telegram Mini App with its own lead back end for a prize promotion: players share their number with one tap and play a game we wrote. See Telegram Mini Apps.
Mobile app development Malaysia, in depth
The supporting detail behind each section of this page, by topic. 4 topics
Building apps on existing systems
Most organisations already run a CRM, a booking system or a member database. We build the app against those systems instead of starting a second record of the same customers.
Enquiries and reminders that run over WhatsApp are built on our WhatsApp automation service, so the app and the chat thread show the same booking.
Native, cross-platform or PWA: which your app should be
| Native iOS and Android | Cross-platform | Progressive web app (PWA) | |
|---|---|---|---|
| Who opens it, how often | Staff or members every day, often in the field | Customers and members on both phone platforms | Occasional users who arrive from a link |
| App Store and Google Play | Listed under your own developer accounts | Listed under your own developer accounts | Installs from the browser; Google Play via a Trusted Web Activity; the App Store only as a wrapped native app that passes App Review |
| Offline use | Yes | Yes | Yes, through a service worker |
| Device features (camera, Bluetooth, location) | Full access | Most, through plugins | Limited by the browser; Web Bluetooth does not work in Safari on iPhone |
| Push notifications on iPhone | Yes | Yes | From iOS 16.4, only once added to the Home Screen and after the user allows it |
| How updates reach users | A store release | A store release | Live when deployed to your server |
| When we recommend it | Heavy camera, location or offline field work | Most booking, membership and internal apps | A tool opened from a link that needs no store listing and little device access |
We decide by asking three things: how often staff or customers open it, whether it must sit in the app stores, and which systems it plugs into. Those systems are usually a CRM or booking back end we build as custom software.
Where bookings and reminders run in chat, the app shares its record with our WhatsApp automation flows.
After launch: stores, ownership and upkeep
Where the app feeds a funnel, sign-ups and bookings are reported back to Meta through the Conversions API and to Google as conversions, so marketing sees which campaigns produced app users.
What we have built
Outside Malaysia, we built the native iOS and Android carrier apps for an Australian freight platform (Ofload).
Explore related services
Frequently asked questions
Should we build native or cross-platform?
Native iOS and Android builds suit apps that lean on the camera, location or offline use in the field. A cross-platform build suits most booking, membership and internal apps, because one codebase serves both stores. We recommend one after discovery, based on what the app has to do.
Can the app work with the systems we already run?
Yes. We integrate the app with the CRM, booking system, WhatsApp flows and back end the organisation already has, so staff keep working in one record instead of two.
Who owns the code?
Ownership of code, accounts and data is agreed in the contract for each project.
Should our app be a PWA or a native app?
shakalakaa recommends a PWA when people open the tool from a link, it needs no store listing and it uses little of the phone.
We recommend native or cross-platform when the app must be in the App Store and Google Play, work in the field or use the camera, Bluetooth or location heavily.
Can a PWA send push notifications on iPhone?
Yes, from iOS 16.4, but only after the user adds the web app to the Home Screen and allows notifications.
Will the app be listed on the App Store and Google Play?
Native and cross-platform apps are, under your own developer accounts. A PWA installs from the browser. It can be listed on Google Play through a Trusted Web Activity, and on the App Store only when wrapped in a native app that passes App Review.
More questions (1)
How is an app project scoped and priced?
Every engagement is a custom quote. We scope the screens, the integrations, the platforms and the support you need after a discovery call, and we do not publish a fixed price.