App Quality Dashboard

join.me

3.9 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 20.89 Sec
  • Launch time: Icon 0.90 Sec
  • Application size: Icon 13.49 MB
  • Last tested on : 26/04/2017
  • Build ID
    :   v3.5.2.5158
  • Chhi Score
    :   3.9
  • Change Rate
    :   -2.5 %

What to fix?

Build v3.4.0.4519 did better in CPU . Spikes in CPU contributed to score drop by 9.38%

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

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.

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

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

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

Utilization of CPU is close to the threshold.

4 tests need immediate attention. View performance graph.

Build v3.4.0.4519 did better in Network . Spikes in Network contributed to score drop by 2.04%

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

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

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

40.33 MB of App Dalvik utilized by activity com.logmein.joinme.JoinMeActivity. View details

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

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

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

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

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

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

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

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

Screen coverage

competition benchmark

This app is ranked #492 in Business

487
488
489
490
491
back-to-top