Official account of NetEase Cloud Music Tech Team
This article shares practical techniques for adapting Android apps to overseas markets, covering modular code design, compliance checks, AAB bundle creation, Google Play signing, manifest adjustments, and automated multi‑language workflows to streamline global publishing.
The guide explains Android debugging fundamentals, covering run and attach modes, essential operations like stepping and breakpoints, best practices for inspecting variables and reducing compile time, the underlying ADB and JDWP protocols, and troubleshooting common issues such as breakpoint loss and port conflicts.
This case study details NetEase Cloud Music's full‑link baseline governance initiative, outlining the challenges of massive data pipelines, the metrics used to measure success, the three‑pronged action plan (infrastructure, task optimization, and standards), and the resulting improvements in availability, resource utilization, and monitoring accuracy.
The article introduces a TypeScript dictionary factory that, using generics and `as const` assertions, converts a single source definition into multiple strongly‑typed representations (KV, VK, list, maps), eliminating duplication and keeping business dictionaries synchronized while providing full IntelliSense, albeit with some TypeScript‑only limitations.
To boost NetEase Cloud Music’s comment handling, the authors combine active‑learning‑driven relabeling, domain‑specific MLM pretraining, contrastive‑learning‑based sample expansion, and multi‑task BERT sharing to raise sentiment‑classification precision and recall above 90 % and double moderation clean‑rate, while employing prompt‑generated story themes, IP‑focused classifiers, and hot‑word aggregation for effective short‑text topic clustering and scalable, theme‑aware distribution.
The paper presents a customizable, dependency‑injected iOS IM framework that separates message‑flow structure from interaction, defines reusable MessageView components with pluggable size‑strategies and a snapshot cache, and exposes standard service protocols, enabling low‑cost integration, business extensibility, and reduced maintenance across diverse chat scenarios.
The paper details Cloud Music’s video‑search pipeline—query understanding, recall, relevance, ranking and re‑ranking—highlighting challenges such as ambiguous content, timeliness and multi‑objective goals, and describes two deployed models (a twin‑tower aspect relevance network and a click‑graph propagator) that together boost click‑through rate by 1.5 % and effective CTR by 2.3 %.
This article explains how NetEase Cloud Music tackled the tight coupling between frontend UI and backend services by introducing a Backend‑For‑Frontend layer built on GraphQL, detailing the architectural choices, low‑code editor, custom directives, deployment pipeline, and the resulting improvements in scalability and developer productivity.
NetEase Cloud Music’s tracking management platform, built on the Dawn Tracking solution, provides a unified, version‑controlled system for client‑side data events that automates code generation, real‑time validation, change visualization, and automatic rebasing, while supporting bridge‑mode integration and aiming to extend into server‑side and hybrid tracking.
This article examines why bundle size matters for front‑end performance and provides a step‑by‑step guide to reducing Webpack output by optimizing Babel polyfills, leveraging @babel/preset‑env, using @babel/runtime, applying tree‑shaking, and eliminating duplicate dependencies.
