- Incorrect layout of the second graph.:
I aimed to provide user friendly interface :) At my point of view it is more clear to have independent axis for independent charts, so user is able to see max and min for each case. 
– Graphs #3 and #5 blinks and jitters when filtering:
It is animation :)
– The scrolling is broken (the attached video):
I realized that such behaviour appears only after switching to zoom. The reason is that position is changed from another thread while the values are not volatile. This means the app takes wrong copy and displays values that are different from calculation. Interesting case, thanks for sharing
Best Regards

Dear colleague, OpenGl is the most efficient technology that can be used for charts with smooth animation and excellent performance, but GLSurfaceView is not on view layer and therefore is not designed for scroll rather fullscreen. I should note that it looks nice on other devices - you're welcome to check screenshot of fast scrolling on Xaomi 5. Best regards and good luck :)

I aimed to provide user friendly interface :) At my point of view it is more clear to have independent axis for independent charts, so user is able to see max and min for each case. Best regards

True, the chart needs margin in this case, thanks for thorough testing   I would be glad to publish update with such tiny ui fixes if the contest assumed support. Best regards!

It would be interesting to look at stacktrace. I tested the same device Samsung Galaxy S4 (Android 5.0.1) in dev lab, but the case is not reproduced. You are welcome to check the vid of my tests http://recordit.co/cLcOlwAHI0
Best Regards.

Right. I worked on optimization. The limitation in range between axis values was applied to enhance performance. It's a good point to recalculate the value on axis in the case the maximum in view port was changed. Thanks.

Thanks

Nice to hear about great performance on Xiaomi Mi5 S   As for the crash: it would be interesting to look at stacktrace. I tested the same device Samsung Galaxy S4 (Android 5.0.1) in dev lab, but the case is not reproduced. You are welcome to check the vid of my tests http://recordit.co/cLcOlwAHI0 By the way, no bugs with scrolling too (reported issue #1) I appreciate your positive attitude! Best regards  

1. Right, but actually there is no big difference in perfomance on #1 and #2 charts, please check GPU on this vid: http://recordit.co/if5hFIPo9Q (no antialiasing) and http://recordit.co/OuLiBSpz1t (antialiasing enabled). As for the #3-5 charts it should be disabled in any case as there is no difference on the result views.
2. No strict requirements can be deducted from provided mockups so alternatives can take place. For example, I did the way you described at the first stage of the contest: http://recordit.co/wcJj9I5Xb0. Also there was a discussion in the contest chat and participants assumed that transparency should depend on a distance between labels. As for me it make sence and should be convinient for users - they are still able to see important data and informed that dates will be gone on zoom action.
3. I found this solution in the app that took #2 place of the stage #1. I like it!

1. I aimed to provide user friendly interface :) At my point of view it is more clear to have independent axis for independent charts, so user is able to see max and min for each case. 
2. Thanks for taking a glance at my work. About the case: easy to fix, just haven't noticed that.
3. Could you be so kind to describe the case in details? I checked it out, the data is shown in proper way - I compared with json and other apps.

1. I haven't seen such case but tested a lot, including remote devices. Were you able to reproduce the case?
2. Right.

Thank you for noticing that. There are two reasons I did the variation. First of all, it allows user to check details for each day while slowly moving the frame of selected area. I found it as a true user friendly approach. You are welcome to check it out: http://recordit.co/w884jhv7A9 (vid of samsung s5/android 6.0.1, black screen - it is lags of recoder app). So in the case you described it will irritate user if details will change the position from time to time. The second reason is that the best UI practices is to have similar behaviour patterns for different cases. Especially, #3-5 charts it's much more convinient way to display data as these charts usually occupy the most of view port. So... it makes sence to have the same on #1-2 charts. Thank you. Best Regards.

Thanks

1, 3: Thanks for sharing videos, they helped me to reproduce the case and understand its nature. I realized that such behaviour appears only after switching to zoom. The reason is that position is changed from another thread while the values are not volatile. This means the app takes wrong copy and displays values that are different from calculation. Interesting case, thanks for sharing :)
2. Right