“How much for an APP?” is as useless as “how much for a workshop.” Who uses it, whether you list it, whether a back office exists—any quote without that is a guess. The ranges below are checkable dimensions, so a cheapest template or a dual-store luxury quote does not drag you.
| Form | Typical cycle | Where the money goes |
|---|---|---|
| H5 / campaign and lookup pages | 2–5 weeks | Pages, forms, existing APIs, analytics |
| WeChat or Alipay Mini Program (one role) | 5–10 weeks | Role flows, pay or subscribe messages, review, one back office |
| iOS + Android APP (with push) | 8–16 weeks | Two platforms, certificates, listing, push, version pipeline, on-device field work |
| Multi-end (employee + customer + store), one back office | 3–6 months | Permission isolation, stock and membership, phased launch—not three separate projects |
The numbers are experience ranges, not a quote. A template mini program can be cheaper, but if fields miss your tickets the structure rewrite comes back. See A template mini program is almost as bad as none. Whether you need native is in When you actually need a native APP.
Why can two “mini program” quotes differ by multiples?
The gap is role count, whether a back office exists, payments, whether you connect inventory or tickets, who supplies content and accounts, and whether data isolates by store. Hidden items: company verification, category review, payment merchant IDs. Without existing APIs, mobile will build the back office too. Do not compare that as “a few pages.”
Can you launch in a week?
What can launch in a week is usually a reskin or a display H5. Scan-and-report, redemption, settlement and weak-network devices will not be solid in seven days. A hollow APP listed just before a bid is the failure path in Why shipping an APP just to “have one” fails. Ship one usable role entry first. Do not spend a week on a store page nobody opens.
Is a dual-platform APP always much more expensive?
Usually yes. Certificates, review, two-platform work and every release stack cost. If users will not download, the expensive part is wasted. See What to do when nobody downloads the APP. Internal high frequency, push and offline make the cost worth it. Customer membership should default to a mini program.
How do you hold budget without shipping a brochure?
Lock roles and the three to five phone actions first. Phase one is the main path only: employee reporting or customer status. Do not also ship a mall, a community and a points shop. Brochure versus work tool is in Brochure mini program versus a work tool. The back office must be one. See one back office.
Count hidden cost or a low price doubles later
Beyond the quote: Apple developer account, store listings, WeChat verification yearly fees, SMS and map quota, payment fees, on-site codes, clerk training. If nobody owns content—point lists, ticket states, SKUs—build stops on waiting. When you compare vendors, make them quote the same role list and say whether connecting current systems and listing help are included. Compare only totals and you are comparing who dares to omit line items.
After discovery DaXi Technology returns scope, phases and an acceptance list—not an unverifiable lump sum. To name users and whether a back office exists, go to the mobile service page and send it. The process overview is in From brief to launch: how a mobile build runs. WeChat or Alipay is in WeChat Mini Program or Alipay Mini Program.