How I Bridged Frontend and Business in 2020: Lessons from Alibaba's Content Creator Platform

Business

Last year Xianyu revived its community content business, and I served as the technical product manager for the creator line, leading both technical and business teammates toward our goals. My work can be summed up in three words: build the team, set goals, make judgments.

Build the Team

Building the team meant uniting technical and business colleagues, aligning their understanding, and establishing trust—a challenging but essential task. For engineers, I considered how to support their growth (business insight, technical depth, etc.). For business partners, I translated their input into actionable technical or non‑technical solutions, fostering trust through daily collaboration.

Set Goals

Goals keep our work aligned with desired business outcomes and user value. While short‑term targets serve the ultimate goal, I emphasized deep thinking about the core objective. Using Amazon’s growth flywheel, I identified creator scale as the key metric, focusing on increasing the number of active creators rather than merely content volume.

Initially I tried to split daily creator numbers like app DAU (new + retained + recalled), but discovered that content publishing has a high user cost and low frequency, making this split misaligned with business actions. Instead, I created dashboards for daily/weekly new (high‑quality) content and channel efficiency, revealing gaps such as rising content volume without corresponding quality improvements.

Business data serves as the simplest way for engineers to understand the product; I encourage building critical metrics and their derivation logic (SQL) to grasp business goals.

Make Judgments

Judgment involves evaluating business needs against ROI and focusing resources on high‑impact areas. For the creator business in its 0‑1 stage, the priority is lowering creation barriers, incentivizing users, and building foundational creator tools.

Foundation products: Creator Center (education/activities) and My Posts (content management/dashboard); admin backend for onboarding and governance.

Lowering barriers: Transform "Xianyu items" that are purely content into publishable posts, similar to the earlier one‑click resale feature.

User incentives: Implement a creator growth system (points, levels, benefits) to drive external motivation.

Serving as the technical PM gave me a CTO‑like perspective, revealing how front‑end work can support business without deep domain‑specific technical breakthroughs, yet highlighting the need for more front‑end‑centric problem solving in the coming year.

Technology

Over the past year I focused on four front‑end initiatives, often intersecting with other tech domains to solve business problems.

Front‑end CEP (Complex Event Processing)

We built a rule engine for matching complex user behaviors, primarily for growth scenarios. The system captures real‑time events, applies rule‑based calculations on the front end, and triggers UI components for user outreach. A server‑side platform manages strategies, data collection, calculation rules, and UI components, enabling dynamic, cross‑page interventions.

Flutter Capability Expansion

In 2020 the Xianyu community front‑end began experimenting with Flutter for business development. Because Flutter’s UI model resembles modern front‑end frameworks, the learning curve for front‑end engineers is modest. However, Flutter’s architecture differs significantly from traditional front‑end stacks, requiring careful integration planning.

Backend Infrastructure

To support the renewed content focus, we launched extensive admin back‑ends for content moderation, creator management, and traffic strategy. We introduced a data‑model‑driven, standardized protocol and a rapid‑page‑generation pipeline: define server data model → select page template → customize UI → generate page.

Container Strategy

Over years, Xianyu’s front‑end has used WebView, Weex, mini‑programs, etc., leading to fragmented knowledge about container capabilities. In FY21S2 we began consolidating container knowledge, deciding to converge dynamic front‑end scenarios onto WebView and improving its performance for FY22.

Future

Reflecting on the past year, I have deepened my business thinking and achieved solid results, yet the translation from business insight to technical implementation remains insufficient. In the coming year I aim to work closely with the team to sharpen business sense, identify problems from a product perspective, and solve them with technical solutions.