App Quality Dashboard

Tinybeans

3.7 / 5

Chhi Score

This app is performing

Average

Medium Risk

/5

Medium Risk

/5

Good 

/5

Good

/5

#

 

Category

Rank

  • Install time: Icon 57.05 Sec
  • Launch time: Icon 1.33 Sec
  • Application size: Icon 50.20 MB
  • Last tested on : 07/04/2017
  • Build ID
    :   v3.11.32
  • Chhi Score
    :   3.7
  • Change Rate
    :   +12.12 %

What to fix?

Build v3.11.31 did better in CPU . Spikes in CPU contributed to score drop by 4%

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.

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

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

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

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

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

Utilization of CPU is close to the threshold.

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

9 tests need immediate attention. View performance graph.

The app's Memory score has improved by 12.9% compared to build v3.11.31! Good job!

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 & Optimize launch time using Flatbuffers for storage and rendering performance.

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

Caching: Use LruCache for data caching to optimize memory usage

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

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

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

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

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

64.41 MB of App Dalvik utilized by activity com.tinybeans.activity.StartActivity. View details

The app's Network score has improved by 2.04% compared to build v3.11.31! Good job!

Screen coverage

competition benchmark

This app is ranked #26 in Parenting

21
22
23
24
25
back-to-top