Reflections on Front‑End Technology, BFF Architecture, and Experience Technology

Apologizing for a somewhat unclear talk at the first Ant Experience Technology SEE Conf, the author writes this article to continue the discussion, noting that designers may skip the front‑end technical sections.

What is front‑end technology? The author, who first encountered front‑end development in 2002, defines it historically as browser‑side HTML, CSS, and JavaScript, emphasizing that front‑end engineers are the programmers closest to users.

Since 2009 the author has worked with Node, witnessing the explosion of front‑end tooling (YUI Compressor → UglifyJS) and the rise of server‑side frameworks like Express. In Ant Financial, Node is often used for the BFF (Backend‑For‑Frontend) layer, which adapts backend services for front‑end consumption.

In the BFF model, back‑end services (often Java) expose domain‑model RPC interfaces; the front‑end calls these APIs, processes data, and handles human‑machine interaction. This architecture enables full‑stack engineers with front‑end backgrounds to focus on domain logic while back‑end teams concentrate on business functionality.

From 2013 onward, Alibaba’s "ALL IN" wireless strategy pushed many front‑end engineers toward iOS (and some toward Android) and massive investment in Mobile Web. The convergence of front‑end and client‑side technologies extended to IoT devices, reinforcing the idea that front‑end work exists wherever users interact with devices.

The author notes that modern mobile architectures increasingly adopt RPC + gateway + BFF patterns, improving development efficiency and network performance. BFF is described not only as a technical architecture but also as a multi‑value, layered approach that encourages cross‑disciplinary collaboration (e.g., DevOps, DesignOps, full‑stack concepts).

The article clarifies that “front‑back separation” is better expressed as “front‑back layering,” emphasizing that each layer should have clear responsibilities and skill requirements.

Returning to front‑end history, the author stresses that the core collaboration boundary is data: back‑end provides services, front‑end consumes them to create user interactions. Different collaboration models (BaaS, BFF, etc.) affect engineering practices such as code standards, workflow, deployment, performance, and security.

With Node and diverse endpoints, front‑end has entered the "big front‑end" era, acting as a connector between back‑end services and user interfaces.

What is experience technology? The author stayed in PC Web front‑end despite the company’s wireless focus. With Alibaba’s "big middle‑platform, small front‑stage" strategy, many enterprise back‑office products suffered from poor UX, prompting the formation of an experience‑technology team that recruited designers.

Design integration changed the author's perspective: front‑end alone cannot solve product‑level UX problems. Good design must dive into business logic, information architecture, and workflow, especially for vertical products with complex terminology.

The team’s focus now includes four directions:

TWA (Techless Web App) : a vision of eliminating concerns about build, deployment, and environment, aiming for a "tech‑less" development experience.

UI Intelligence : leveraging Ant Design and Ant Design React (antd) to explore intelligent visual UI construction.

Data Visualization : building visual tools (e.g., G2, AntV) since 2014 to reduce cognitive load and improve computation speed.

Graphic Interaction : creating interactive graphic interfaces for gamified public‑service experiences such as Ant Forest.

Looking ahead, the author predicts two major trends for experience technology: natural interaction and virtualization. Natural interaction would allow gestures (e.g., nodding) to trigger actions like slide changes, while virtualization extends beyond AR/VR to fully immersive, multi‑sensory interfaces.

Experience technology is summarized as the formula UX = f(services) , turning backend services into high‑quality user experiences through the fusion of technology and design, exemplified by Ant Experience Cloud.

Ant Experience Cloud, still in its early stage, already serves internal Ant Financial and Alibaba services and has spun off products such as Cloud Phoenix Butterfly, Yuque, and Little Money Bag. The author invites the community to join the journey of building more equitable opportunities through open experience technology.

Thank you for listening; the author looks forward to further exchanges.

Video of the SEE Conf talk is available on Youku, and the presentation PDF can be downloaded from the SEE Conf Yuque knowledge base (registration required).