App Quality Dashboard

LEXI24

1.5 / 5

Chhi Score

This app is performing

Poor

Medium Risk

/5

High Risk

/5

High  Risk

/5

Medium Risk

/5

#

 

Category

Rank

  • Install time: 12.43 Sec
  • Launch time: 1.49 Sec
  • Application size : 3.53 MB
  • Last tested on : 11/06/2017
  • Build ID
    :   v2.6.2
  • Chhi Score
    :   1.5
  • Change Rate
    :   0%

What to fix?

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by Motorola might experience a crash on their phone!. Fix now!

Motorola Moto E (2nd gen) crashed at info.jourist.lexi24.ui.FragmentDict.setup2(FragmentDict.java:838) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by Panasonic 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.

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Zenfone 2 Laser crashed at info.jourist.lexi24.ui.FragmentDict.setup2(FragmentDict.java:838) View details

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by LYF might experience a crash on their phone!. Fix now!

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by Asus might experience a crash on their phone!. Fix now!

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

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

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

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by Micromax might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Motorola Moto E (2nd gen), Zenfone 2 Laser & more devices. View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: info.jourist.lexi24 PID: 10157 java.lang.NullPointerException: A... Users with phone manufactured by YU might experience a crash on their phone!. Fix now!

14 tests need immediate attention. View performance graph.

2 Risk(s) are due to App Total in Memory exceeding the threshold.

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

Utilization of CPU is close to the threshold.

Utilization of Memory is close to the threshold.

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

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

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

41.35 MB of App Dalvik utilized by activity info.jourist.lexi24.Main. View details

Caching: Use LruCache for data caching to optimize memory usage

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

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

7 Tests crashed out of 21 Tests. Check where the app crashed. View details

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

318 apps having similar CPU load have low Chhi Scores

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

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

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!

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

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

competition benchmark

This app is ranked #1420 in Books & Reference

1415
1416
1417
1418
1419
back-to-top