App Quality Dashboard

WhistlePhoneFinderFast

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 5.50 Sec
  • Launch time: 0.00 Sec
  • Application size : 2.25 MB
  • Last tested on : 16/06/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

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

Must fix: App crashed because of 6561): FATAL EXCEPTION: main 6561): Process: com.da.whistle.phone.finder.fast PID: 6561 6561): ... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!

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.

Lenovo A6000 crashed at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3647) View details

Samsung Duos Galaxy J7 crashed at android.app.ActivityThread.handleSleeping(ActivityThread.java:4921) View details

Oops!, The app crashed on Samsung Duos Galaxy J7, Lenovo A6000 & more devices. View details

Must fix: App crashed because of 6561): FATAL EXCEPTION: main 6561): Process: com.da.whistle.phone.finder.fast PID: 6561 6561): ... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!

Your App Memory 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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

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

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

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

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

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

6 Tests crashed out of 6 Tests. Check where the app crashed. View details

144 apps having similar CPU load have low Chhi Scores

competition benchmark

This app is ranked #1096 in Productivity

1091
1092
1093
1094
1095
back-to-top