MyJio 将 ANR 问题减少了 40%,客户投诉量因此而降低
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
MyJio 是通向 Jio 产品和服务世界的门户。这里是充值、管理账户和 Jio 设备、UPI 和付款,以及提供电影、音乐、新闻、游戏、测验等娱乐服务的一站式平台。MyJio 是印度最大的应用之一,安装量超过 5 亿,月活用户数超 1.5 亿。
此外,随着 JioPhone NEXT(Jio 的低成本 4G 智能手机)的推出,一个最近从非智能手机迁移的新用户细分群体也日渐盛行。
为了迎合如此庞大的用户群,即使只影响 1% 的用户的性能问题,也会影响到 500 万用户。因此,为了提升应用性能和用户体验,Google Play 采取了大幅的举措。
面临的挑战
由于 MyJio 的 ANR 和崩溃指标在许多不同 Android 版本的中低端设备上运行,因此该应用的 ANR 和崩溃指标受到了冲击。要想在继续为各种设备提供支持的同时提供无缝的客户体验,并非易事,其中一些设备搭载的是旧版和已废弃的 Android 版本。此外,确保应用在最低端的 Android Go 设备上顺畅运行也是该团队的首要任务。
调试需要花费相当长的时间,因为日志数量有限,很难再现这些场景。
这些挑战也直接影响了 MyJio 的变现策略。一个重点领域是,确保应用内的操作流程顺畅运行,并减少 ANR 错误。这样,用户就可以充值、发掘潜在客户、通过 UPI 进行交易以及完成其他各种活动,而不必担心应用没有响应。
具体做法
为了分析各种设备硬件配置下由 ANR 和崩溃导致的瓶颈,MyJio 团队依靠 Play 管理中心、Android Studio(用于开发和调试)、Firebase Crashlytics 等工具。
该团队采取有针对性的方法来解决以下问题:
- 识别了广播 ANR、重组 ANR 以及由于设备(尤其是内存较低的设备)上呈现线程块而导致的 ANR。
- 观察到与 Compose 相关的 ANR,根据堆栈轨迹,这些 ANR 妨碍了信息中心的呈现。
- 在 Play 管理中心观察到 ANR 问题后,他们在 Android Studio 中检查了 MyJio 应用的严格模式,然后逐一解决那些会阻塞主线程的问题。
- 在 Firebase Crashlytics 中启用了疾速崩溃提醒错误报告,以便立即突出显示所有异常情况。
- 第三方 SDK 的集成受到密切监控,因此它们占用主线程的时间超过 300 毫秒。
成果
在实施这些更改时,MyJio 团队必须留意各种设备配置。他们还必须考虑到新用户的涌入,从非智能手机升级到 JioPhone NEXT 4G 智能手机。
该团队取得了以下成效:
- 应用运行缓慢、崩溃和 ANR 方面的用户反馈减少了 20%。这直接意味着用户的会话时间缩短了 15%
- ANR 发生率降低了 40%
- 热启动时间缩短了 70%
- Play 商店评分提高了 18%
- 会话时长缩短了 15%
团队的速度和工作效率总是在提高,看到这些提升成效显著提升了团队的士气。
“为用户提供一流服务是 Jio 与 Google 共同的愿景。这种合作伙伴关系帮助我们借助 JioPhone Next 进一步践行了以客户为中心的理念,从而为尚未开发的用户群带来新的数字革命。随着越来越多的用户加入我们的用户群(包括受众特征、设备和 Android 版本),我们必须为所有用户(尤其是数字世界的新参与者)提供体验和优化服务。”
- Mohsin Abbas,MyJio 客户和合作伙伴渠道产品和工程副总裁兼主管
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# MyJio reduces customer complaints by lowering ANRs by 40%\n\nMyJio is the gateway to the world of Jio products and services. It is the-one-stop destination for recharges, managing accounts \\& Jio devices, UPI \\& payments, entertainment services with movies, music, news, games, quizzes \\& a lot more. With over 500Mn installs and 150Mn MAUs, MyJio is one of the largest apps in India.\n\nMoreover, with the introduction of the JioPhone NEXT (Jio's low-cost 4G smartphone), a new user segment, recently migrated from feature phones, came into the pie.\n\nCatering to such a huge user base, a performance issue affecting even 1% of users translates into 5 million users. The magnitude, thus, invited a dedicated effort in enhancing the app performance and user experience.\n\nThe Challenge\n-------------\n\nMyJio's ANR and crash metrics were taking a hit due to the app being present in a large number of mid and low-end devices spread across Android versions. It was a challenge to provide a seamless customer experience while continuing to support a variety of devices, some of which were running on older and deprecated Android versions. It was also a priority for the team to ensure the app runs smoothly on the lowest end Android Go device.\n\nDebugging took considerable time as the logs were limited in number and it was very difficult to reproduce the scenarios.\n\nThese challenges directly impacted MyJio's monetization strategy as well. An important area of focus was to make the journeys inside the app seamless and have lesser ANRs. This way users could recharge, generate leads, transact via UPI and various other activities without any hassle of the app not responding.\n\nHow They Did It\n---------------\n\nTo analyze the bottlenecks created by ANRs and crashes across various device hardware configurations, the MyJio team relied on Play Console, Android Studio (for development and debugging), Firebase Crashlytics, and more.\n\nThe team took a targeted approach to address the following issues -\n\n- Identified Broadcast ANRs, Recompose ANRs, and ANRs due to rendering thread block on devices (particularly low memory devices).\n- Observed Compose related ANRs which were hampering the rendering of Dashboard as per the stack trace.\n- After observing ANRs on Play Console, they checked MyJio app on strict mode in Android Studio and proceeded to fix the issues one by one which were blocking on the main thread.\n- Enabled velocity alerts error reporting on Firebase Crashlytics so that any anomalies get highlighted immediately.\n- Integration of third party SDKs was watched closely so that they do not occupy the main thread for more than 300ms.\n\nResults\n-------\n\nThe MyJio team had to be mindful of the various device configurations while implementing these changes. They also had to take into account the influx of new users, upgrading from feature phones to the JioPhone NEXT 4G smartphone. \n\nThe team achieved the following results -\n\n- 20% reduction in user feedback with respect to app slowness, crashes and ANRs. This directly translated into improved session time of users by 15%\n- Improvement in ANR rate by 40%\n- Hot startup time improved by 70%\n- Play Store ratings improved by 18%\n- Improvement in session time by 15%\n\nTeam velocity and productivity are always on the rise, and seeing these improvements come to fruition boosted the team's morale even more.\n\u003e \"The obsession to provide best-in-class services to users is a vision that is\n\u003e shared between Jio and Google. This partnership has helped us take the\n\u003e customer-centricity further with JioPhone Next; allowing a new digital\n\u003e revolution for an untapped set of users. With more \\& more users being\n\u003e onboarded acrross demographics, devices and android versions, it becomes\n\u003e imperative that experience and optimisations be made for all users, especially\n\u003e the new entrants in the digital world.\"\n\u003e\n\u003e **-- Mohsin Abbas, VP - Head of Products \\& Engineering for Customer \\& Partner Channels, MyJio**"]]