Skip to content
Since98
Insights · Build

Zalo Mini App vs mobile app: which one should your business build first?

A Zalo Mini App opens inside Zalo, so customers use it without installing anything. A native app lives on the phone home screen and can do more with the device. The right first step depends on how often customers come back, what the app must do offline and who will maintain it.

02 — Short answers

Short answer

Should a business in Vietnam build a Zalo Mini App or a mobile app first?

Short answer
Start with a Zalo Mini App when your customers already message you on Zalo and need a few simple actions: booking, ordering, checking a status, showing a member card. Build a native app when customers use it often, need offline work, push-heavy features, deep device access or a brand experience outside Zalo.
How we do it
We compare the jobs the app must do against what runs well inside Zalo, then check the platform rules for your category before any design work.
Limits
Zalo sets the review process and rules for Mini Apps, and they can change. We confirm them in the Zalo documentation at the start of each project; this article does not replace that check.

What each option is

A Zalo Mini App is a small web application that opens inside the Zalo app. The customer taps a link, a QR code or a button in your Zalo Official Account and the Mini App opens without a download. It can use the customer's Zalo identity, with their consent, so they do not create another login.

A native mobile app is installed from the App Store or Google Play. It has its own icon, its own login and full access to what the phone allows: camera, location, notifications, offline storage and background tasks. It works the same whether or not the customer uses Zalo.

Both can talk to the same backend: your booking system, CRM or order database. The difference is where the customer meets you and how much the phone itself is involved.

Side by side

The table compares the two on the points that usually decide the choice. It describes typical cases; your requirements can move a row either way.

Zalo Mini App and native app compared
QuestionZalo Mini AppNative mobile app
How customers get itOpens inside Zalo from a link, QR code or your OAInstalled from the App Store and Google Play
LoginCan use the Zalo account with the customer's consentOwn login, or sign-in with Google, Apple or phone
Best forShort, occasional tasks: book, order, check, show a cardDaily or weekly use, rich features, offline work
Device featuresLimited to what Zalo exposes to Mini AppsFull access the operating system allows
Customers outside ZaloNot reachable unless they use ZaloReachable on any phone
Release processZalo review rulesApple and Google review rules
Who controls the platformZaloApple and Google

When a Mini App is the better first step

A Mini App fits when the habit is already there. If your customers write to your Zalo OA to ask about prices and slots, a Mini App turns that conversation into a few taps without asking them to install anything.

  • A clinic, spa or restaurant that wants booking and reminders where customers already chat
  • A shop that wants a simple catalog and order form linked from its OA
  • A loyalty card or member page that customers open a few times a month
  • A pilot to test whether customers use self-service at all before paying for a native app

When you need a native app

A native app makes sense when the app is the product, or when customers use it often enough to keep it on the home screen.

  • Customers use it daily or weekly: delivery tracking, field staff, learning, fitness
  • It must work without a connection, then sync later
  • It needs device features beyond what Zalo offers to Mini Apps, such as background location or Bluetooth
  • You serve many foreign customers who do not use Zalo
  • You need full control over design, release timing and the customer relationship

Doing both, in order

Many businesses do not have to choose forever. A common path is to start with a Mini App or a simple web page linked from Zalo, learn which actions customers repeat, and only then build a native app around those actions.

If the backend is built cleanly, with an API that does not care which screen calls it, the second front end costs less because the booking, order and customer logic already exist. We design the backend that way from the first version.

Five questions that settle the choice

Answer these before you ask anyone for a quote. They usually make the choice obvious.

  • How often will one customer open it: a few times a year, a month or a week?
  • Where do your customers contact you today: on Zalo or on other channels?
  • Must anything work offline or in the background?
  • Who will maintain it after launch, and in which language?
  • What happens to the data: which system is the source of truth for bookings, orders and customers?

Risks to plan for

Each option depends on a platform owner. A Mini App depends on Zalo's rules, review and the features it exposes. A native app depends on Apple and Google reviews and on regular updates for new operating system versions.

For both, personal data needs a plan: what you collect, why, where it is stored and how customers can ask for it to be deleted. We agree that with you, and with your lawyer where needed, before launch.

Zalo's Mini App rules, review steps and fees are set by Zalo and can change. We check the current documentation at the start of a project rather than quoting them from memory.

03 — FAQ

Questions readers ask

Can a Zalo Mini App send notifications?

Customers can receive messages through your Zalo Official Account, within Zalo's rules for OA messages. What a Mini App can trigger, and on which conditions, we confirm in the Zalo documentation for your case.

Can we turn a Mini App into a native app later?

The screens are usually rebuilt, but the backend, data and business logic can stay. That is why we keep the backend separate from the first version.

Is a Mini App cheaper than a native app?

It is usually smaller in scope, because it does fewer things and runs on one platform. The quote depends on the features, so we price it after a short scoping call.

Who owns the Mini App and its data?

It is published under your business's Zalo account and the data sits in your systems. We set it up in your name, not ours.

04 — Sources

Sources and notes

  1. 01Zalo Mini App platformOfficial entry point; current rules, review and features are checked there at project start
  2. 02Our experience building web and mobile appsFounders' experience building web and mobile apps
05 — Author

Who wrote this

Dmitry KaplanEngineering · Mobile · In software since 2008

One of the two founders of Since98. We write about what we set up for clients: what works, what it costs and where the limits are.

About the founders
06 — Articles

Read next

  • Build · 4 min read

    Mobile app developer cost

    What decides the cost of a mobile app, fixed price versus time and materials, and the costs that come after release.

  • AI & Automation · 4 min read

    AI chatbot on Zalo OA: setup steps

    The setup order for an AI chatbot on a Zalo Official Account: accounts, webhook, permissions, reply rules and hand-off.

  • AI & Automation · 4 min read

    Zalo OA, ZNS and Bot API

    OA messages, ZNS, Mini Apps and personal Zalo compared: who starts the message, what each needs and where each stops.

08

Next step

Describe the situation in a few lines. One of the founders replies and says whether we can help and what the first step would be.

Discuss your project
Or write in a messenger: