App Quality Dashboard

Track my phone: cell finder

1.6 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

Medium  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 9.85 Sec
  • Launch time: 4.00 Sec
  • Application size : 3.75 MB
  • Last tested on : 21/04/2017
  • Build ID
    :   v0.1
  • Chhi Score
    :   1.6
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobmedics.mobile_finder.tracker PID: 26801 java.lang.RuntimeExce... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: mobmedics.mobile_finder.tracker PID: 26801 java.lang.RuntimeExce... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

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

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

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.

13 Risk(s) are due to App PSS in Memory exceeding the threshold. See how to optimize memory and remove 13 High Risk(s).

The app took 4.00 seconds to load on Android OS version 5.0.2. Usually anything more than 3.2 seconds results in user drops. View details

Utilization of CPU is close to the threshold.

17 tests need immediate attention. View performance graph.

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

The app has crashed on few device(s)! 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.

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

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

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

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

41.45 MB of App Dalvik utilized by activity mobmedics.mobile_finder.tracker.Splash. View details

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

98 apps having similar CPU load have low Chhi Scores

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

Screen coverage

competition benchmark

This app is ranked #552 in Communication

547
548
549
550
551
back-to-top