Download .APK (1.2 MB)

Testing and Issues

You can test this app and submit issues during the testing period of the Android Chart contest.

Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.


by rating


Fair Mammoth Apr 28, 2019 at 13:51
– Overall speed is average.
– The third and the fifth graphs are slow when filtering.
– Switching themes causes the screen to blink.
– The design does not fully comply with the guidelines (e.g. data filters change their positions).
LG Nexus 5X, Android 8.1.0; Samsung Galaxy J7, Android 8.1.0
Groovy Puma Apr 28, 2019 at 14:54
Selected points change their position while scaling.
Galaxy J5 (2016) Android 5.1.1
Filtering graph #5 is critically slow.
Samsung Galaxy S4, Android 5.0.1
Very poor performance on the area chart: frame drawing time greatly exceeds 16ms.
Nexus 5 / Android 6.0.1
Sharp Turtle Apr 17, 2019 at 22:16
Area charts made with paths and it's not hardware acc. it could be improved by switching to openGL.

Performance really depends on device and OS.

Agree that overall this particular chart could be improvement by getting rid of non hw acc. path approach.
Button changes its position
Sharp Turtle Apr 17, 2019 at 21:59
Since design of active & inactive button have different width ('done' mark width is the issue) there is no way to keep them in the same places after toggling.
2. Y scaled chart. Y scaled wrap animation is shart. Also, auto wrap logic is calculated in the wrong way at some point (2nd video).
Umi Super, Android
Sharp Turtle Apr 17, 2019 at 22:04
Thx for the review.
In terms of wrong calculation - in my implementation I just compute boarded values +- threshold (to show lines beyond real borders) and also computes it's values as max/min possible, that's why it could be scaled awkward at first glance (min/max value is out of the visible bounds).

It could be a bugs or a future depends on requirements.
3a. Stack Bar Chart. Strange empty spaces at the edges of the preview widget (apply to all charts) (pointed on video with touch).
3b. 0 value Y-line also always animated but should be static
Sharp Turtle Apr 17, 2019 at 22:35
3a. It comes from requirements:
there is a range selection on control view and we need to make some assumprion about which part of the control should correlate to which part of real graph - the start/end of draggable control OR start/end of mask between draggable controls. According to provided designs and plain logic I've decided that start/end of control should correspond to graph and in that case we need margins from side in control to have consistent state between chart and control view (chart has margin as per designs)

3.b Agreem forget to disable this animation, my bad, thx.
I would disagree with Fancy Starfish. Performance is quite good. Why performance of widget could not be judged on stack bar overlays (first screenshot here) you could read Dreamy Griffin answer (#50)

But this app does have issues.
1. Again. Wrong Auto Height Wrap logic. I think the problem is due to throttling. (Good performance but wrong logic). I think that at first place logic and calculation must be correct. And only then steps must be taken to improve performance. Not vice versa.
Umi Super, Android, API 23
Sharp Turtle Apr 17, 2019 at 22:14
It's not a bug it's a feature ;) see my answer below. But again, thx for such accurate testing and bug reporting, appreciate it!
5. Percentage Stack Bar. Sometimes filtering/appear/disappear animations could be ended abruptly. Also for Stack Bar Charts.
Samsumg X Cover 3, Android
Sharp Turtle Apr 17, 2019 at 22:12
Agree, I have the same timer for animation, if you start animation it take ~400ms for animation and even you start next animation afterwards it should be in the same time frame (within the same 400ms) and e.g. is you start next collapsing one at 399ms you just have 1ms to collapse line.
4. Stack Bar Chart "Views". Edges are calculated (and shifted) SLIGHTLY wrong during expanding/narrowing.
See left edge relatively to zero. At the biggest scale chart's first bar start coincides with zero text start, but at the lowest scale, bar start coincides approximately zero center
Sharp Turtle Apr 17, 2019 at 22:10
Sorry but I don't get your point but again thx for a review!
Nobody added any issues yet...