App Quality Dashboard

myHomework

1.8 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

High Risk

/5

#

 

Category

Rank

  • Install time: Icon 21.22 Sec
  • Launch time: Icon 1.19 Sec
  • Application size: Icon 9.23 MB
  • Last tested on : 22/05/2017
  • Build ID
    :   v4.3.9
  • Chhi Score
    :   1.8
  • Change Rate
    :   -43.75 %

What to fix?

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

Build v4.3.1 did better in Memory . Spikes in Memory contributed to score drop by 9.68%

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

Build v4.3.1 did better in CPU . Spikes in CPU contributed to score drop by 8.33%

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

1 Risk(s) are due to Data Sent/Received in Network 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.

Potential risk in Network: Utilization has gone up by62.22% compared to build v4.3.1

App size increased by 61.08% See how to optimize.

7 tests need immediate attention. View performance graph.

Consider re-merging the code from build v4.3.1, Network score was 4.5

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

Utilization of Network is close to the threshold.

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

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

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

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

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

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

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

Network utilization on Lenovo VIBE K4 Note exceeded 1024 KB, you might want to consider bringing it down

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

Caching: Use LruCache for data caching to optimize memory usage

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

Your average App Dalvik usage surged by 8.22%, Your memory score is 2.8

App makes 1032.48 KB of network requests. Moving this to a background thread will improve load speed. View details

66.91 MB of App Dalvik utilized by activity com.myhomeowork.homework.AddHomeworkActivity. View details

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

Total Network data consumed was 1032.48KB in Lenovo VIBE K4 Note , This indicates the app will take 10-15 seconds on 2G network and 8-9 seconds on 3G network to load! View details

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

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

Screen Coverage

competition benchmark

This app is ranked #1962 in Education

1957
1958
1959
1960
1961
back-to-top