How Personalized Design, Features, and Content Boost Mobile App Success

This article examines how detailed user demand differences shape personalized design, functional, content, and service elements in mobile apps, illustrating why catering to specific scenarios and user states is crucial for standing out in a competitive market.

JD.com Experience Design Center
JD.com Experience Design Center
JD.com Experience Design Center
How Personalized Design, Features, and Content Boost Mobile App Success

Meeting user needs is the foundation of a good user experience for a product, feature, design, or service. However, user demands vary widely, and seemingly identical needs often differ in subtle details, especially across different contexts or psychological states.

When researching, designing, or developing products, we tend to address the majority's generalized needs while overlooking nuanced differences—such as customizing a ringtone to meet specific timing preferences—or atypical scenarios, like using a music app as an alarm.

In today's fiercely competitive market with abundant products and converging functionalities, capturing these nuanced demands and fulfilling atypical, scenario‑specific needs becomes a key factor for an app to differentiate itself.

Design Layer

In theory, any design element of an app—icons, themes, background skins, interaction effects, information architecture, etc.—carries a potential for personalization. Yet most apps only offer limited personalization such as theme or wallpaper settings, while comprehensive design customization remains rare.

Functional Layer

Functional personalization involves features that users can actively customize based on their personal information or behavior, as well as automatic presentation of personalized information. True recommendation‑based functional personalization is still uncommon.

Content Layer

Content personalization is a major focus for many apps and can be categorized as follows:

Personalization based on interests , e.g., customized news columns in NetEase News.

Personalization based on past behavior , e.g., Taobao’s “You May Also Like” recommendations.

Personalization based on life scenarios , e.g., scene‑based music recommendations in Baidu Music.

Personalization based on geolocation , e.g., radar friend‑adding in WeChat.

Personalization based on physiological traits , e.g., training courses in Keep tailored to user height and weight.

Service Layer

Service‑level personalization mainly concerns apps that sell physical goods or offline services. While standardization and personalization are often contradictory, personalization should start from detailed user needs and atypical requirements, offering differentiated service at each touchpoint. Currently, most service personalization remains at a generic differentiation level, such as JD.com’s multiple delivery options.

In summary, app personalization primarily focuses on three aspects: functional customization, content customization, and content recommendation. Design‑level personalization, functional recommendation, and service‑level customization are still insufficient, but as personalization attempts and technologies evolve, the scope for app personalization will continue to expand.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

User experiencecontent recommendationmobile designapp personalizationfeature customization
JD.com Experience Design Center
Written by

JD.com Experience Design Center

Professional, creative, passionate about design. The JD.com User Experience Design Department is committed to creating better e-commerce shopping experiences.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.