App Quality Dashboard

eRecorder

0.4 / 5

Chhi Score

This app is performing

Poor

Memory

High Risk

/5

CPU

Medium Risk

/5

crash

High  Risk

/5

network

Good

/5

Competition

#

 

Category

Rank

  • Install time: 4.20 Sec
  • Launch time: 1.31 Sec
  • Application size : 1.58 MB
  • Last tested on : 30/03/2017
  • Build ID
    :   v1.1
  • Chhi Score
    :   0.4
  • Change Rate
    :   0%

Insights (29)

What to fix?

Oops!, The app crashed on Karbonn Titanium Machfive, Zenfone 2 Laser & more devices. View details
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
Must fix: App crashed because of FATAL EXCEPTION: main Process: eapps.pro.erecorder PID: 31872 java.lang.RuntimeException: Unabl... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: eapps.pro.erecorder PID: 31872 java.lang.RuntimeException: Unabl... Users with phone manufactured by Lenovo might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: eapps.pro.erecorder PID: 31872 java.lang.RuntimeException: Unabl... Users with phone manufactured by Samsung might experience a crash on their phone!. Fix now!
Zenfone 2 Laser crashed at android.app.ActivityThread.handleStopService(ActivityThread.java:3077) View details
Karbonn Titanium Machfive crashed at android.app.ActivityThread.handleStopService(ActivityThread.java:3093) View details
Must fix: App crashed because of FATAL EXCEPTION: main Process: eapps.pro.erecorder PID: 31872 java.lang.RuntimeException: Unabl... Users with phone manufactured by Panasonic might experience a crash on their phone!. Fix now!
Must fix: App crashed because of FATAL EXCEPTION: main Process: eapps.pro.erecorder PID: 31872 java.lang.RuntimeException: Unabl... Users with phone manufactured by Asus 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.
The app's memory score is 1.7 due to high memory utilization. Needs to be fixed as priority.
The app has a high performance risk for the phone manufacturer(s) Samsung, Lenovo, Karbonn, Panasonic, Asus. Check coverage report for more details.
6 tests need immediate attention. View performance graph.
Utilization of CPU is close to the threshold.
Testability: Providing login / sign-up details could very well improve depth of bot clicks
Do not initialize objects that aren't necessary during launch times. Moving to singleton pattern helps
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
Follow simple UI hierarchy by reducing nested layouts to Relative layouts.
10 Tests crashed out of 10 Tests. Check where the app crashed. View details
Fix Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.
Fix & Optimize launch time using Flatbuffers for storage and rendering performance.
There is high probability of identifying risks running the apps with conditions
Printing logs on callbacks would make debugging easy for tests run in our platform
132.85 MB of App Dalvik utilized by activity eapps.pro.erecorder.MainActivity. View details
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.
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
Unlock more fixes

Screen Coverage

competition benchmark

This app is ranked #1219 in Business

1214
1215
1216
1217
1218
back-to-top