A Zalo mini app can go from idea to launch in 30 days if the business picks one compact problem (booking, loyalty, ordering, lookups), already has a verified Zalo Official Account, and assigns one decision-maker who reviews weekly. The Zalo platform handles the hardest parts: an existing user base, login with the Zalo account, integrated payment. This article is the week-by-week roadmap Siri9 uses, with reference costs and the places where schedules usually slip.
What a Zalo mini app is good for
A mini app runs inside Zalo; customers do not download anything from an app store. It suits tasks customers do often but briefly:
- Booking: clinics, spas, salons, car service, classes.
- Loyalty points and member offers: coffee chains, restaurants, retail.
- Reordering: recurring purchases such as water, gas, groceries.
- Lookups: order status, warranty, delivery schedule, points balance.
- After-sales: notifications, reviews, support requests.
It is not suited to apps that need deep phone capabilities (advanced camera, background processing, heavy computation). Those belong to a mobile app. If your customers are mainly on Zalo, starting with a mini app is always cheaper and faster.
Before day 1: three things that must be done
The 30-day schedule only holds if these three are complete before you start:
- A verified Zalo Official Account (OA) for the business. Verification requires the business license and takes several working days; without a verified OA you cannot publish a mini app.
- One problem, one main flow. For example "customers book and receive reminders", not "booking, loyalty, sales and chat". The second feature goes in the next version.
- A decision-maker on the business side who can spend 2 hours a week on reviews.
Week 1: lock the scope and design
Days 1 to 2, lock the flow. Sketch on paper the screens a customer passes through from opening the mini app to finishing the task. For booking this is usually 5 screens: choose service, choose date and time, confirm, done, my bookings. For each screen note the data needed and what happens on each tap.
Days 3 to 5, interface design. Use Zalo Mini App's standard UI kit so customers find it familiar and review passes quickly. The business reviews the design at the end of the week; changes now are cheap, changes in week 3 cost many times more.
In parallel, prepare the data. Service list, prices, opening hours, branches, cancellation policy. This is the business's job, and it is usually the latest item.
Week 2: build the core
The development team builds the server side (database, APIs) and the main screens per the approved design. The key point this week is connecting to the business's existing systems: sales software, inventory, CRM. A mini app must not become a data island; an order placed in the mini app must appear where staff already work.
By the end of week 2 the business sees a test build on a real phone and walks the full main flow. Not polished yet, but it must work end to end.
Week 3: Zalo integration and polish
- Login with Zalo: open and use, no sign-up. The mini app asks for name and phone number only when needed, not up front.
- Payment: if you sell, integrate a Zalo-supported payment gateway; if it is booking only, pay-at-counter is fine for the first version.
- Notifications: booking reminders, order confirmations, new points via OA messages. This is Zalo's big advantage over a website: messages reach the right customer with high open rates.
- Staff admin page: view bookings, confirm, change status. Usually a simple web page or a connection into existing software.
End of week 3: internal testing with 5 to 10 staff, recording every confusing spot.
Week 4: testing, review and launch
Days 22 to 24, fix bugs and final testing on multiple Android and iPhone devices, weak networks, fresh Zalo accounts.
Day 25, submit for review. Zalo reviews mini apps before they go public; this usually takes a few working days. The submission needs a description, screenshots, a privacy policy and a test account for reviewers. Rejections are usually for requesting unnecessary permissions or missing a privacy policy.
Days 28 to 30, soft launch. Open to a group of loyal customers via OA message, watch the first 48 hours, fix fast, then announce widely.
After day 30: what decides success
Many mini apps "die" after the first month not because they were built badly but because nobody operates them:
- Nobody answers support requests inside the mini app.
- Bookings are not confirmed in time and customers lose trust.
- Zalo updates the platform, one function breaks, nobody notices.
- The backend server expires or runs out of disk.
That is why Siri9 always hands over with an operations plan: server monitoring, backups of booking and customer data, updates when Zalo changes its SDK, and a ticket channel for the business to request changes. Details on mini app development and custom software maintenance.
Reference costs
- Development: from around 20 million dong for a basic booking or loyalty mini app; with ordering and payment from 40 million; deep integration with existing software priced by scope. Fixed quotes per scope, not hourly.
- Monthly operations: a few hundred thousand dong for the server, plus a maintenance plan from 3,000,000 dong a month for a mini app.
- Zalo fees: publishing is free; OA messaging and payment have Zalo's own fee schedule.
Where schedules slip
- OA not verified at the start: adds 1 to 2 weeks. Do it first.
- Features added mid-project: every added feature is another week. Put it on the version 2 list.
- Business data not ready: prices, schedules, branches. Set a day-5 deadline.
- Legacy software without an API: needs investigation time; flag it in week 1.
- Review rejection: request few permissions, include a privacy policy, provide a test account.
Frequently asked questions
How is a Zalo mini app different from an App Store or Google Play app?
A mini app runs inside Zalo, needs no install, reuses existing accounts and payment, and launches in weeks. A native app is stronger on device features but costs more, takes longer and must acquire its own users. Many businesses start with a mini app and build a native app once they have a customer base.
Can a mini app become a standalone app later?
Yes. The backend, data and business flows carry over almost entirely; only the phone interface is rebuilt.
What does the business need to prepare technically?
Nothing beyond a verified Zalo OA and access to existing software (if a connection is needed). All source code, server accounts and the mini app itself are owned by the business at handover.
How do we start?
Send a description of the problem (booking, loyalty, ordering or lookups) and the channels your customers use; Siri9 advises on the right platform and returns a fixed quote within 24 hours. If you are weighing a mini app against a web app, from spreadsheets to smart systems compares the roadmaps.