Phone Tracker

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

High Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 24.50 Sec
  • Launch time: Icon 2.65 Sec
  • Application size: Icon 24.22 MB
  • Last tested on : 05/05/2017
  • Build ID
    :   v13.6.0
  • Chhi Score
    :   1.8
  • Change Rate
    :   0%

What to fix?

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.

Fixing CPU risks could drastically improve Chhi Score. There are 18 CPU risks.

Your App CPU is now in a High Risk Zone. With a small investment into your testing you can improve your app quality better. Get more test coverage

Potential risk in CPU: Utilization has gone up by 11.76% compared to build v13.4.0

18 Risk(s) are due to Threads in CPU exceeding the threshold.

Utilization of CPU is close to the threshold.

18 tests need immediate attention. View performance graph.

The app's Memory score has improved by 3.57% compared to build v13.4.0! Good job!

The app has a high performance risk for the phone manufacturer(s) LYF, Lava, Micromax, YU, Lenovo, Panasonic. Check coverage report for more details.

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

347 apps having similar CPU load have low Chhi Scores

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

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

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

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

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.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

61.26 MB of App Dalvik utilized by activity com.life360.android.first_user_experience.login_screens.CreateAccountPhoneActivity. View details

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

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

Screen Coverage

competition benchmark

This app is ranked #1610 in Tools

1605
1606
1607
1608
1609
back-to-top