App Quality Dashboard

Zoho People

2.9 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk




Medium Risk






  • Install time: Icon 11.50 Sec
  • Launch time: Icon 1.49 Sec
  • Application size: Icon 8.60 MB
  • Last tested on : 10/05/2017
  • Build ID
    :   v3.1.3
  • Chhi Score
    :   2.9
  • Change Rate
    :   -6.45 %

What to fix?

Build v3.1.2 did better in Memory . Spikes in Memory contributed to score drop by 6.9%

App launch time went up by 65.56% initlizate network calls after few seconds of loading the resources. View details

Test more often so that you don't break the CPU handling further in your next builds. CPU Score is in danger zone. Heavy battery consumption expected.

The app has a high performance risk for the phone manufacturer(s) Motorola, YU, Asus, Lenovo. Check coverage report for more details.

4 tests need immediate attention. View performance graph.

The app's CPU score has improved by 6.9% compared to build v3.1.2! Good job!

Testability: Providing login / sign-up details could very well improve depth of bot clicks

Coverage: Android version coverage for reports will range between 5.1.1 to 7.1.2

Optimize the app to render elements at 60 FPS for buttery smooth experience.

Caching: Use LruCache for data caching to optimize memory usage

Upload APKs with and without 3rd Party SDKs to monitor and optimize the impact of app performance

There is high probability of identifying risks running the apps with conditions

Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps

Printing logs on callbacks would make debugging easy for tests run in our platform

35.86 MB of App Dalvik utilized by activity com.zoho.people.activities.LoginActivity. View details

Follow simple UI hierarchy by reducing nested layouts to Relative layouts.

Fix & Optimize launch time using Flatbuffers for storage and rendering performance.

Below 10 MB approach would increase app installs in crowded markets such as India, China and Russia!

Avoid wake-locks in background, using Batch and schedulers APIs such as GCM, Job schedulers could reduce wake-locks

Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

Screen Coverage

competition benchmark

This app is ranked #919 in Business