Growth Methodology for Mobile Apps: Acquisition, Retention, A/B Testing, and Deep Linking

Shaozhen, a former Google Search engineer and Square full‑stack engineer, shares his experience on mobile growth, emphasizing that growth is about achieving effective business expansion rather than the sensational notion of “growth hacking.”

Growth is defined as the systematic pursuit of business growth, combining tools and thinking, and has become especially popular in China due to intense market pressure and the need for efficiency in engineering, acquisition, and monetization.

The core topics of growth are divided into four parts—user acquisition, conversion, monetization, and retention—often represented by the AARRR model, which highlights the interdependence of each stage rather than a simple funnel.

Effective growth relies on a disciplined experimental loop: observe user behavior patterns, formulate hypotheses, define measurable metrics, implement engineering solutions, monitor results, and iterate based on data insights.

Engineers play a pivotal role because they understand product implementation, instrumentation, and performance constraints, making them the most efficient drivers of growth experiments.

A minimal growth unit should include engineering, product, data, design, and operations talent; even if one person covers multiple roles, the necessary expertise must be present.

Strategic alignment is crucial—growth should be prioritized over pure technical difficulty, and rapid iteration, even with small experiments, helps accumulate significant impact over time.

Mobile‑specific opportunities include the device being a personal entry point, continuous user tracking, and the ability to deliver value without mandatory login, while challenges involve limited cross‑linking, longer release cycles, and difficulty conducting A/B tests.

User onboarding is illustrated as a funnel where each step (download, login, registration, core‑feature use, repeat usage, payment) incurs user loss; optimizing each drop‑off point—through ASO, anonymous onboarding, push notifications, and frictionless payment—improves overall conversion.

Traditional funnel analysis can be overly user‑centric; instead, viewing each stage as a measure of user willingness and adjusting the experience to increase that willingness yields better results.

Key mobile growth technologies are presented, starting with an A/B testing system architecture that includes a splitter, logging pipeline, metric calculation, dashboards, and QA controls, all designed to minimize user‑experience impact and ensure statistical validity.

Deep‑linking (including deferred deep‑linking) is explained as a way to bypass the App Store entry point, enabling direct navigation to specific content and reducing user loss, though implementation requires careful handling of URL parameters and third‑party services.

Content dynamization is discussed through feature flags, template‑driven pages, and server‑driven workflows, balancing the cost of flexibility against testing complexity.

In conclusion, growth is a real, widely‑used practice that requires incremental, low‑cost experimentation, leveraging third‑party tools when possible, and focusing on high‑impact, low‑effort improvements to achieve sustainable business growth.