App Quality Dashboard

Clap To Find My Phone

3.4 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: 10.08 Sec
  • Launch time: 0.85 Sec
  • Application size : 3.55 MB
  • Last tested on : 11/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   3.4
  • Change Rate
    :   0%

What to fix?

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

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.

Utilization of CPU is close to the threshold.

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

6 tests need immediate attention. View performance graph.

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.

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

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

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

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

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

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

78.98 MB of App Dalvik utilized by activity com.jvstudios.claptofindmyphone.InstructionsActivity. View details

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

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

Screen coverage

Test Flows YU Yuphoria Karbonn Titanium Machfive Micromax Canvas A1 Lenovo VIBE K4 Note Lenovo A6000 Motorola Moto E (2nd gen)

Install app

  • Success

  • Success

  • Success

  • Success

  • Success

  • Success

Scenario 1

  • Risk

  • Success

  • Risk

  • Risk

  • Risk

  • Risk

Scenario 2

  • Risk

competition benchmark

This app is ranked #1017 in Tools

1012
1013
1014
1015
1016
back-to-top