App Quality Dashboard

FireEffect Photo Maker

3.6 / 5

Chhi Score

This app is performing


Medium Risk


Medium Risk


Medium  Risk








  • Install time: Icon 12.70 Sec
  • Launch time: Icon 0.87 Sec
  • Application size: Icon 9.16 MB
  • Last tested on : 22/03/2017
  • Build ID
    :   v1.2
  • Chhi Score
    :   3.6
  • Change Rate
    :   -7.69 %

What to fix?

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

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

Must fix: App crashed because of 8477): FATAL EXCEPTION: main 8477): Process: com.jvr.fireeffect.photomaker PID: 8477 8477): jav... Users with phone manufactured by Karbonn 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.

Utilization of CPU is close to the threshold.

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

10 tests need immediate attention. View performance graph.

Motorola Moto E (2nd gen), Samsung Duos Galaxy J7, Karbonn Titanium Machfive has moved from Good to Medium risk due to FAIL . View details

The app's CPU score has improved by 30% compared to build v1.0! Good job!

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.

3 Tests crashed out of 20 Tests. Check where the app crashed. View details

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

The app has crashed on few device(s)! View details

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

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.

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

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

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

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

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

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

50.51 MB of App Dalvik utilized by activity View details

Caching: Use LruCache for data caching to optimize memory usage

The app's Network score has improved by 4.88% compared to build v1.0! Good job!

Well done, Network consumption has come down by 19.1 % compared to build v1.0

Screen Coverage

competition benchmark

This app is ranked #446 in Photography