App Quality Dashboard

TheTimeMachine

0.1 / 5

Chhi Score

This app is performing

Poor

Memory

CPU

High  Risk

/5

network

#

 

Category

Rank

  • Install time: 7.33 Sec
  • Launch time: 0.00 Sec
  • Application size : 1.23 MB
  • Last tested on : 14/05/2017
  • Build ID
    :   v1.0
  • Chhi Score
    :   0.1
  • Change Rate
    :   0%

What to fix?

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.

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

Karbonn Titanium Machfive crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2455) View details

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

Lenovo A6000 crashed at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2308) View details

Must fix: App crashed because of FATAL EXCEPTION: main Process: appinventor.ai_msthao2010.TheTimeMachine PID: 18417 java.lang.Ru... 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: appinventor.ai_msthao2010.TheTimeMachine PID: 18417 java.lang.Ru... 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: appinventor.ai_msthao2010.TheTimeMachine PID: 18417 java.lang.Ru... Users with phone manufactured by Karbonn might experience a crash on their phone!. Fix now!

Oops!, The app crashed on Lenovo A6000, Karbonn Titanium Machfive & more devices. View details

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

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

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

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

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

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

Fix & Optimize launch time using Flatbuffers for storage and rendering 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 Oncreate() if the launch time is exceeding more than 3.2 secs. Try deflating views and layouts to optimize.

318 apps having similar CPU load have low Chhi Scores

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

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

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

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

competition benchmark

This app is ranked #1634 in Books & Reference

1629
1630
1631
1632
1633
back-to-top