← All Posts

焕新360手机卫士:从工具到情感伙伴Revitalizing 360 Mobile Security: From a Mere Tool to an Emotional Companion

一份产品复盘:用五周时间焕新360手机卫士,从数据研究到7.0改版,让日活和留存重新回升。A product case study: five weeks to revitalize 360 Mobile Security, from cohort research to a redesigned 7.0 that turned DAU and retention around.

Context#

The daily active users for 360 Mobile Security, a one-stop application that consists of an anti-virus, system cleaning, and other features, declined by 15%, and the 30th-day retention rate dropped by 3% from early 2016 to late 2017. Additionally, the active launch rate declined by 12%. A revisit of the vision, planning, features, and design of the application was necessary to save it.

I was the product management lead for the reviving project. Along with my design and dev team, we finished the entire project in 5 weeks.

Get Ready: Project Timeline#

We have to ship out our first beta version in 45 days. A thorough schedule would significantly benefit us in achieving our goal.

Project timeline Gantt chart, April 12 to May 27: research, design, and development tracks running in parallel, with a quality gate on May 3 and the beta version shipped on May 27. APR.12 APR.15 APR.20 APR.22 MAY.03 MAY.27 Research Design Develop Quality Beta Version Shipped Kick Off & Schedule Actuality Research User Research Market Research QA Analysis & Vision UX / Logic Design Former Design Review Prototyping & Iteration Technology Probe Interface Dev. Server Dev. Performance Dev.

Look into Data: Discover Existing Problems#

The cohort analysis was the principal part of our research. We have a relatively sophisticated data collection system, and using user data to evaluate the way users interact with our app is one of the best methods to identify problems and determine our further research direction.

Stacked bar chart, Weekly User Constitution: share of new users falls from 59% in the first week of October to 29% in the first week of March, while consecutive multi-week users grow. Weekly User Constitution 0% 25% 50% 75% 100% First week of Oct. First week of Nov. First week of Dec. First week of Jan. First week of Feb. First week of Mar. New Users Yesterday Users This Week Return Users Consecutive Users in Different Weeks *Our absolute number of weekly new users was steady
  • The percentage of new users was less than anticipated. A downtrend in the percentage of new users indicates that the rate of initial function satisfaction among new users was falling.
  • A low frequency of functional usage was also a possible reason that could lead to the low two-week and four-week succession user percentages and the high return user percentage.

  • We conducted more in-depth research with the help of the freshness degree of users. The steadiness of the 30th-day freshness user rate indicates that most active users are satisfied with our products.
  • The previous second-day freshness user rate declined sharply compared to the first-day freshness user rate, but the +4 and later day freshness user rates were relatively steady. We suggest that it was the unfriendly function guides that caused new users to leave.

The sharp decline in the 2nd to 3rd step user access pattern further confirmed our hypothesis.

Most functions require 3+ clicks to reach, which makes the learning cost of our product quite high and scares away new users. The conversion rate of users after two clicks declined gradually, indicating that those users knew what they were doing and were willing to do it.

User Research: To Comprehend Users in an Emotional Way#

At this phase of user research, we focused more on the use cases of our audience in addition to data, such as their usage habits, the problems they encountered, and their emotional feedback. Moreover, we hope to gather more ideas from users.

We synthesized our user research and user data and identified four insights that led to the heart of the matter. These realizations helped us refine our hypothesis and determine the specific areas and issues that our solution needs to target.

  • Some users did not know when or how they should use 360 Mobile Security.
  • Users became upset when a function was the reason they installed our app.
  • Users experienced a lag on their phones after installing 360 Mobile Security.
  • Some users complained that our product lacks functions that they want or that our competitors have.

Malfunction and performance problems can influence the retention rate and can be fixed by our R&D and QA teams alone without changes in the logic and user interface after we describe the specific situation (we made these problems our priority). Product managers then move forward to identify additional problems and new improvement points.

Market Research: Inspired by the Market#

Competitor Analysis#

We analyzed our main competitors and identified their strengths and weaknesses. We paid additional attention to their new features and experiences that are lacking in our product.

Industrial Analysis#

We discovered several current market and user demand situations after reviewing reports issued by iResearch, QuestMobile, Analysys, and TalkingData.

iResearch
Using Apple HIG to design Android apps is more popular than using MD Guideline.
QuestMobile
System-based user demands are declining fast. Users pay more attention to content and are more unwilling to think about a function’s logic than they had been before.
TalkingData
The popularization of the 4G network and diversified data plans make attention to data balance more and more necessary. Always-online functions are also becoming possible due to improvement in the average device’s performance.
Analysys 易观
Young people are more willing to use Tencent Mobile Manager than 360 Mobile Security or choose not to use a smartphone security app.

Analysis & Vision: Combined Solutions with Innovative Ideas#

We revised our current functions by combining user emotion with their potential demands. When new ideas emerged during our research, we found the direction for our new version.

Prototyping & Usability Test: Do We Have the Same View as the Audience?#

We redesigned our app structure by making function levels flatter and creating a clearer and more user-friendly design for new users.

We sketched medium-fi prototypes and completed usability tests with each iteration. We primarily used hotspot maps and path maps to evaluate our design. The prototypes for the eighth iteration are as follows.

In our eighth usability test:

  • 81% of users went directly to their desired functions instead of spending time searching for them.
  • The +3 click function reach rate dropped from 22% to 6%.
  • The bounce rate of the main page decreased from 32% to 17%.

Afterward, we created the Hi-Fi version of our designs and sent them to the development team.

Design: Putting Thoughts into Reality#

Give the Main Page a Feed#

We redesigned our main page to be waterfall-like in order to make young users feel more comfortable exploring new features and their phone statuses.

The 7.0 version main page feed.

Ideogram: We removed all unnecessary copywriting and redesigned the icons to be more concise. Our aim was to indicate the places where users want to go more clearly.

Focus: We reorganized our functions, made more room for our main features, and improved the perception of our brand image.

Structure revision makes functions easier to get in touch with.

Old function entry in the 6.x version.

New function tab on the 7.0 version main page.

Skins for Young Users#

We represented brightness not only in our designs but also in our functions. We made our functions customizable.

Additionally, we redefined the functions we provided, positioning ourselves as a true and sincere friend and phone manager.

  • Users can customize their desired functions in the toolbox.
  • Suitable features will be promoted based on user tags and operating behaviors.
  • In the 6.x version, functions were hidden in a drawer menu and were unchangeable.

Combined with real-time detection and our push system, our users no longer have to worry about when to clean their phones, check for software updates, or deal with other annoying issues.

One of our advantages is that we have many safety-related features from other departments that are tightly integrated in our app, more so than in other apps.

Data Performance: The Ultimate Way to Evaluate Our Product#

We analyzed our data performance every week after shipping our beta version. After five weeks…

DAU/Return User Improvement
Return Users Percentage increased by 11%
DAU increased 1.1% from declined 15%
Retention Improvement
Grouped bar chart, Retention Improvement: Day 1 retention 39.1% on the 7.0 beta versus 33.9% on 6.x and 30.0% industry average; Day 7: 18.1%, 13.7%, 11.0%; Day 30: 8.9%, 5.0%, 5.5%. 39.1% 33.9% 30.0% Day1 Retention 18.1% 13.7% 11.0% Day7 Retention 8.9% 5.0% 5.5% Day30 Retention
Retention Rate on 7.0 Beta VersionRetention Rate on 6.x VersionIndustry Average
Positive User Behaviors Improvement
4.1 Active Functions
Average Function Usage on 7.0 Beta Version
2.9 Active Functions
Average Function Usage on 6.x Version
Bar pair, Function Usage Frequency Improvement: 2.6 times per day before, 3.9 times per day after. Before 2.6 Times/Day After 3.9 Times/Day
Function Usage Frequency Improvement

We were able to prevent our Daily Active Users from declining, and our DAUs even increased by 3.1% compared to the original data.

Finally, our 30th Day Retention Rate also increased by 3.9%, indicating that three million more users kept the 360 Mobile Security app on their phones after 30 days.

Please feel free to try 360 Mobile Security 7.x here with an Android phone!

背景#

360手机卫士是一款集杀毒、系统清理等功能于一体的应用。从2016年初到2017年底,它的日活跃用户下降了15%,第30日留存率下降了3%,主动启动率也下降了12%。要挽救这款产品,必须重新审视它的愿景、规划、功能与设计。

我是这个焕新项目的产品负责人。带着设计和开发团队,我们用5周时间完成了整个项目。

准备就绪:项目排期#

我们必须在45天内发布第一个测试版。一份周密的排期表对达成目标大有裨益。

项目排期甘特图,4月12日至5月27日:研究、设计、开发三条线并行推进,5月3日进入质量阶段,5月27日测试版发布。 4月12日 4月15日 4月20日 4月22日 5月3日 5月27日 研究 设计 开发 质量 测试版发布 启动与排期 现状调研 用户研究 市场研究 QA 分析与愿景 交互 / 逻辑设计 旧版设计回顾 原型与迭代 技术预研 界面开发 服务端开发 性能开发

深入数据:发现现存问题#

同期群分析是我们研究的核心。我们拥有相对完善的数据收集体系,而通过用户数据来评估用户与应用的交互方式,是发现问题、确定后续研究方向的最佳方法之一。

堆叠柱状图,每周用户构成:新用户占比从10月第一周的59%降至3月第一周的29%,跨周连续活跃用户占比上升。 每周用户构成 0% 25% 50% 75% 100% 10月第一周 11月第一周 12月第一周 1月第一周 2月第一周 3月第一周 新用户 昨日用户 本周回流用户 跨周连续活跃用户 *每周新增用户的绝对数量保持稳定
  • 新用户占比低于预期。新用户比例的下行趋势说明,新用户对初始功能的满意率正在下降。
  • 功能使用频率偏低也是一个可能的原因,它会导致两周和四周的存续用户占比偏低、回流用户占比偏高。

  • 我们借助用户新鲜度指标做了更深入的研究。第30日新鲜度用户比例保持平稳,说明大多数活跃用户对我们的产品是满意的。
  • 相比第1日,第2日的新鲜度用户比例出现骤降,但第4日及之后的数据相对平稳。我们推测,是不友好的功能引导把新用户劝退了。

用户访问路径中第2步到第3步的急剧下滑,进一步验证了我们的假设。

大多数功能需要点击3次以上才能到达,这让产品的学习成本变得很高,把新用户吓跑了。而两次点击之后用户的转化率是缓慢下降的,说明这些用户清楚自己在做什么,也愿意继续操作。

用户研究:从情感层面理解用户#

在这个阶段的用户研究中,除了数据,我们更关注用户的使用场景,比如他们的使用习惯、遇到的问题以及情绪反馈。同时,我们也希望从用户那里收集更多的想法。

我们把用户研究与用户数据加以综合,提炼出四个直指问题核心的洞察。这些洞察帮助我们修正了假设,明确了解决方案需要瞄准的具体方向和问题。

  • 一些用户不知道什么时候、该怎么使用360手机卫士。
  • 当某个功能正是用户装机的理由时,它出问题会让用户格外恼火。
  • 用户安装360手机卫士后,手机出现了卡顿。
  • 一些用户抱怨产品缺少他们想要的功能,或竞品已有的功能。

故障和性能问题会影响留存率,而这类问题只需我们向研发和测试团队描述清楚具体情况,不需要改动逻辑和界面就能修复(我们把这些问题列为最高优先级)。产品经理则继续向前,去寻找更多问题和新的改进点。

市场研究:从市场中获取灵感#

竞品分析#

我们分析了主要竞争对手,梳理出它们的优势与短板,并格外留意那些我们产品尚且缺失的新功能和新体验。

行业分析#

在研读了艾瑞、QuestMobile、易观和TalkingData发布的报告后,我们对当前的市场格局和用户需求有了新的认识。

iResearch 艾瑞
Apple HIG 来设计 Android 应用,比使用 MD 规范更加流行。
QuestMobile
系统级的用户需求正在快速衰减。用户比以往更关注内容,也更不愿意去思考功能的逻辑。
TalkingData
4G 网络的普及与多样化的流量套餐,让用户越来越有必要关注流量管理。设备平均性能的提升,也让常驻在线的功能成为可能。
易观 Analysys
年轻人更愿意使用腾讯手机管家,或者干脆不使用手机安全类应用,而不是选择 360 手机卫士。

分析与愿景:让解决方案与创新想法相结合#

我们把用户情感与潜在需求结合起来,修订了现有功能。研究过程中不断涌现的新想法,也为新版本指明了方向。

原型与可用性测试:我们和用户看到的是同一个产品吗?#

我们重新设计了应用结构,把功能层级变得更扁平,为新用户提供更清晰、更友好的设计。

我们绘制了中保真原型,并在每次迭代后进行可用性测试,主要用热点图和路径图来评估设计。第八轮迭代的原型如下。

在第八轮可用性测试中:

  • 81%的用户直接找到了想要的功能,而不再需要花时间寻找。
  • 需要3次以上点击才能到达功能的比例从22%降到了6%。
  • 主页跳出率从32%降到了17%。

随后,我们完成了高保真设计稿,并交付给开发团队。

设计:把想法变成现实#

给主页一个信息流#

我们把主页重新设计成瀑布流式,让年轻用户能更自在地探索新功能和手机状态。

7.0版本的主页信息流。

图形化: 我们删掉了所有多余的文案,把图标重新设计得更简练,目的是让用户想去的地方一目了然。

聚焦: 我们重新组织了功能结构,给主要功能留出更多空间,同时强化品牌形象的感知。

结构上的修订让功能更加触手可及。

6.x旧版本的功能入口。

7.0版本主页上的新功能页签。

为年轻用户准备的皮肤#

我们不仅在设计上体现明快,也把这种明快带进了功能:我们让功能变得可定制。

同时,我们重新定义了所提供的功能,把自己定位成一位真诚的朋友和手机管家。

  • 用户可以在工具箱里定制自己想要的功能。
  • 系统会根据用户标签和操作行为,推荐合适的功能。
  • 而在6.x版本中,功能都藏在抽屉菜单里,且无法更改。

配合实时检测和推送系统,用户再也不用操心什么时候清理手机、检查软件更新,或者处理其他烦人的琐事。

我们的一大优势在于,应用里深度集成了许多来自其他部门的安全能力,这一点远超其他同类应用。

数据表现:评估产品的终极方式#

测试版上线后,我们每周分析一次数据表现。五周之后……

DAU / 回流用户改善
回流用户占比提升 11%
DAU 由下滑 15% 转为增长 1.1%
留存改善
分组柱状图,留存改善:次日留存 7.0 Beta 版 39.1%,6.x 版 33.9%,行业平均 30.0%;7日留存 18.1%、13.7%、11.0%;30日留存 8.9%、5.0%、5.5%。 39.1% 33.9% 30.0% 次日留存 18.1% 13.7% 11.0% 7日留存 8.9% 5.0% 5.5% 30日留存
7.0 Beta 版留存率6.x 版留存率行业平均
用户积极行为改善
4.1 个活跃功能
7.0 Beta 版人均功能使用
2.9 个活跃功能
6.x 版人均功能使用
柱状对比图,功能使用频次改善:改版前每天 2.6 次,改版后每天 3.9 次。 改版前 2.6 次/天 改版后 3.9 次/天
功能使用频次改善

我们成功止住了日活跃用户的下滑,DAU甚至比原先增长了3.1%。

最终,第30日留存率也提升了3.9%,这意味着有三百万名用户在30天后仍把360手机卫士留在手机里。

欢迎用安卓手机点击这里体验360手机卫士7.x!

Comments