Why can one app quote cost ten times another?
“Build an app” is not a unit of work. A CNY 30,000–50,000 quote can reasonably describe a templated single-client product or a very narrow MVP. CNY 300,000–500,000 can reasonably describe bespoke iOS/Android delivery, administration, APIs, integrations, and production readiness. Normalize clients, business journey, and quality responsibility before comparing totals. These ranges are illustrations, not Wavesteam pricing or a market benchmark.
| Delivery | Typical content | Not included by default | Main cost driver |
|---|---|---|---|
| White-label/template | Brand replacement, fixed sections, existing admin, few fields | Deep rules, broad source rights, complex integrations | License, configuration, submission, light testing |
| One-journey MVP | Login, one core task, basic admin, essential APIs | Full marketing suite, complex roles, full migration | Product design, clients/backend, critical-path tests |
| Production custom product | iOS/Android, admin, API, payment/message/data, monitoring, handover | Unagreed clients, modules, and continuing operations | Multi-role work, exceptions, compatibility, security, integrations |
When defining budget, scope, and cost assumptions, also compare Why can software quotes for the same request differ by several times?; the linked guidance adds context that should be considered in the same decision.
A WebView shell, Flutter/UniApp product, and two native apps can all be called an app while carrying different delivery and upgrade work. Cross-platform code reduces some duplication but still needs platform permissions, push, payment, signing, devices, store materials, and operating-system updates.
Decompose the quote into product and interaction; mobile behavior including offline and accessibility; backend and administration; payments, identity, enterprise, devices, or AI integrations; data and migration; functional, compatibility, performance, and security quality; store release; and repositories, CI/CD, monitoring, deployment, and runbooks. Invisible quality work materially affects production and review.
Android's core app quality guidance covers state restoration, accessibility, stability, compatibility, permissions, security, and representative device tests. Apple's review guidelines cover safety, performance, business, design, and legal requirements. Third-party memberships, infrastructure, messaging, maps, payments, models, content licenses, and test devices remain separate and change over time.
Page count is a poor effort unit. A static page may take little work; one payment button includes order creation, signing, callback, idempotency, refund, reconciliation, compensation, and audit. “Add AI” may mean one API call or knowledge curation, retrieval, evaluation, permissions, cost controls, and human takeover.
The client supplies market, critical user task, existing systems and data, timing, budget, and representative volume. Wavesteam derives the recommended native or cross-platform route, client/admin scope, normal and exception flows, interfaces, migration, load and quality targets, permissions, store accounts, handover, warranty, and operations. For competitive bids, each supplier fills the same roles, effort, assumptions, exclusions, and third-party costs.
If the lower quote meets that same schedule with credible evidence, buy it. If it covers only a shell, it is not comparable to a production custom delivery. Wavesteam's About page states mobile capabilities, but the project proposal, prototype, integration proof, and test matrix must justify the actual route.