Start early: the items with waiting times
Most launch delays come from accounts and approvals, not code. Start these as soon as the build begins:
- D-U-N-S number: both stores need one for organisation accounts. Google warns that getting one can take up to 30 days (Google Play Console Help).
- Google Play testing rule: new personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers for 14 consecutive days before going to production (Google Play Console Help). Another reason to publish under your company.
- Payment gateway approval: gateways check your company documents, bank account and website before going live. Timelines vary by provider, so apply as soon as your company and website are ready.
- Store review: Apple says it reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours (Apple App Review). Google says some apps face extended reviews of up to seven days or longer (Google Play Console Help). Plan at least a week of buffer.
Company and accounts in the company's name
Register the company with SSM
A Sdn Bhd is the usual choice for an app business that may raise funding. Open a company bank account.
Get a domain and work email
Apple requires a working website on a domain associated with your organisation, and a work email on that domain (Apple Developer enrolment).
Enrol in the Apple Developer Program as an organisation
You need a D-U-N-S number, legal entity status and the authority to sign for the company. The fee is US$99 per membership year.
Create a Google Play organisation account
Also needs a D-U-N-S number. There is a US$25 one-time registration fee (Google Play Console Help).
Own every other account
Code repository, cloud hosting, domain, analytics, email sending, maps and payment accounts should all be in the company's name, with founders as admins. Use multi-factor login and a shared password manager.
Legal pages, PDPA and e-invoicing
- Privacy policy: Apple requires a link in App Store Connect and inside the app (App Review Guidelines 5.1.1). Under the PDPA, the notice must be in Bahasa Malaysia and English. See PDPA for apps.
- Google Play Data safety form: declare what data the app collects and shares (Google Play Console Help). It must match your privacy policy and what the app actually does.
- Terms of use and refund policy: payment gateways and customers will look for them.
- Account deletion: if users can create an account, Apple requires that they can delete it from within the app.
- Consent and marketing opt-in: separate checkboxes, recorded with a timestamp.
- E-invoicing check: businesses below RM3 million in annual turnover are generally exempt, but marketplaces and group companies may not be. See LHDN e-invoicing for apps and confirm with your tax agent.
Payments
- Choose methods Malaysians use: FPX online banking, DuitNow QR, cards and popular e-wallets. Check which ones your gateway supports and its fees.
- Know the app store rules. Unlocking digital features or content inside an iOS app (subscriptions, premium content, in-game currency) must use Apple's in-app purchase. Physical goods and services used outside the app, such as food, rides or bookings, must use other payment methods (App Review Guidelines 3.1.1 and 3.1.3(e)). Google Play has its own payments policy, so check it too.
- Prepare the gateway application: SSM documents, company bank statement, a live website with terms, privacy and refund policies, and a description of what you sell.
- Test end to end: successful payment, failed payment, refund, duplicate callback and a slow network. Make sure orders and payments reconcile daily.
Quality, analytics and crash reporting
- Crash reporting in both apps and error monitoring on the backend, with alerts going to a person, not just a dashboard.
- Analytics events defined in advance: sign-up, the first key action (activation), purchase or booking, and cancellation. If you do not decide these before launch, you will not have the data later.
- Uptime monitoring for the API and website, and tested database backups.
- A staging environment that matches production, so you can test fixes before release.
- Test on real devices common in Malaysia, including mid-range Android phones and slower connections, not only the latest iPhone.
- A demo account for reviewers if the app needs a login, with the backend switched on (App Review Guidelines 2.1).
App store listing
Name, subtitle and keywords
Use the words your customers search, in English and Bahasa Malaysia where relevant. Avoid other brands' trade marks.
Screenshots that sell
Show the main benefit in the first two screenshots, with short captions. Follow each store's current size requirements.
Description and support links
A clear first paragraph, a support URL, a privacy policy URL and a contact email that someone reads.
Age rating and content declarations
Answer the questionnaires accurately; wrong answers are a common cause of rejection or removal.
Release controls
Use manual release, so you choose the launch moment after approval, and a staged rollout on Google Play to catch problems with a small share of users first.
Soft launch, support and launch marketing
Soft launch first. Release to a limited group, such as your waitlist, one city in the Klang Valley, or a few business customers, for a few weeks. Fix the crashes and confusing steps before you spend on marketing.
Set up customer support on WhatsApp. Malaysian users expect it. Use a WhatsApp Business number owned by the company, set reply hours, prepare saved replies for common questions, and link to it from the app and store listing. Log every issue so the product team sees patterns.
Plan the launch. Build a waitlist while you build, line up launch-day messages to that list, partner and community posts, founder content on LinkedIn and TikTok, and a small paid budget to test channels. See finding your first customers, setting a marketing budget and TikTok marketing for startups. If you want help running ads, our ads team manages over RM600,000 a year in client ad spend across Google and Meta.
| What it tells you | Watch it | |
|---|---|---|
| Activation rate | Share of sign-ups who complete the first key action | Daily in the first weeks |
| Day 1, 7 and 30 retention | Whether people come back without being pushed | Weekly, by sign-up week |
| Conversion to paid | Whether the product is worth paying for | Weekly |
| Crash-free users | Stability across devices | Daily, and after every release |
| Cost per acquisition | What each new customer costs by channel | Weekly, per channel |
| Store rating and reviews | Early warning of bugs and confusion | Daily; reply to every review |
Pick three of these as your launch scorecard and review them every week with the team. If activation or retention is weak, fix the product before you increase marketing spend.
Frequently asked questions
How long does App Store review take?
Apple says it typically reviews at least half of submissions in under 24 hours and 90% in under 48 hours. Incomplete submissions take longer or are rejected. Google Play reviews can take up to seven days or longer for some apps, so allow at least a week.
Do I need a D-U-N-S number to publish an app in Malaysia?
Yes, if you publish as an organisation. Both Apple and Google require a D-U-N-S number for organisation developer accounts. Google warns it can take up to 30 days to get one, so apply early.
Should I publish the app under my own name or my company?
Your company. The seller name on the store comes from the account, investors expect the company to own its accounts, and Google's 12-tester, 14-day testing rule applies to new personal accounts.
Do I need a privacy policy to publish an app?
Yes. Apple requires a privacy policy link in the store listing and inside the app, Google requires a Data safety declaration, and the PDPA requires a privacy notice in Bahasa Malaysia and English.
What should I track after launching an app?
Start with activation, retention, conversion to paid, crash-free users, cost per acquisition and store ratings. Review three of them every week.