Snowball Cross-Platform Architecture: RN and WebView Container Overview

With the rapid growth of mobile internet, Snowball faces challenges such as slow client release cycles, duplicated iOS/Android development, and high engineering complexity of native solutions. To address these, Snowball has adopted a cross‑platform container architecture that unifies RN, WebView, and native containers.

The architecture is organized into five layers: system services (iOS/Android), infrastructure services (network, base libraries), container layer (RN, WebView, native containers), business layer (community, fund, stock services), and the top‑level apps (Snowball App and Snowball Fund App). This layered design enables code reuse, platform abstraction, and consistent business logic across multiple endpoints.

The RN container builds on React Native, adding dynamic update capabilities, dual‑platform reuse, and extensive tooling (scaffolding, templates, component libraries, multi‑level code splitting, monitoring, and fallback mechanisms). It also provides a bridge to align RN with the WebView container, ensuring a unified development experience.

The WebView container focuses on page‑level support, offering a standardized UI, navigation, loading states, and a robust JSBridge that defines native‑to‑JavaScript communication. It includes offline H5 loading, performance monitoring, white‑list security, and business‑specific enhancements.

JSBridge serves as the core communication mechanism, standardizing method calls across Android, iOS, different Snowball platforms, and containers. It registers handlers in a map, processes JSON‑encoded requests from H5, executes native logic, and returns results via JavaScript callbacks.

Native components such as FundCard, Lottie, Reanimated, ViewPager, LinearGradient, SNBPullToRefresh, Svg, FlashList, and Toast complement the containers by providing high‑performance UI elements that are difficult to achieve purely in JavaScript.

Looking ahead, Snowball plans to refine fine‑grained operation (e.g., DSL‑based dynamic frameworks), improve container performance (addressing JavaScript execution bottlenecks), and open the container capabilities to external developers through an mPaaS platform.