– it isn't relative on the second graph.

Second graph works the way it was described in the announcement:
> The Y-scale on line graphs should start with the lowest visible value (Screenshot 4).
Two series are related to each other by the ratio of preview chart to correlate to it as much as possible.

– The latest date is partially cut on the first graph (the attached screenshot).

The case is you didn't move the range to the right side far enough — it can be seen on the screenshot you attached.

– Bonus goal is completed, but zoomed chats scrolling is slow, the data point info is static on the pie chart.

I really hope you didn't assume that zoomed charts scrolling is slow in terms of fps, it just works that way: you are scrolling between days as discreta ranges. This behavior was taken from the GIF attached.

Yes it is. I was using "y_scaled" field provided in the json, so as chart #2 provides it, it is scaled correctly

Thank you!

Nice catch! It is a bit unfortunate, one wrong if statement :) Appears on the second chart too. Fortunately it recovers if you enter to zoomed mode again

You right, transition looks a bit rough.

When implementing it I just followed animation guideline from android developers: "Whenever possible, your animations should apply real-world physics so they are natural-looking."

So what you're seeing is how physics works for pears bar. It could be different, but behavior consistency would be lost :)

I found a Zenfone to appreciate this most liked review :)
Here is a video with gpu bars attached. It is not 60 fps, but it is definitely not 15-20 fps as well.

Yes, last chart was a hardest part to optimize without loosing quality. I was using Nexus 5 as one of the target devices and noticed that performance wasn't that good as well, but it looked slightly better than in the video provided.

Anyway, thanks for your comment, means a lot!

X labels are animated. You can slow down the animation (Developer Options -> Animation duration scale) or the video to notice that.

About confusing distribution: it's kinda controversial :) I used an algorithmic approach that works for any kind of range and dates, it is determenistic (not random) and doing a nice job in my opinion.

Thank you for the comprehensive review! I mostly agree with your comments but going to leave some replies anyway :)

I've already adressed this question, I really think this thing is kinda subjective. You can like it or not, but this is not really an issue or BAD UX :)

Nevertheless you right, it might be done better.

Yeah, I figured my paddings were quite big comparing to other works :) But again, I disagree with your "incorrect" statement. It is just a way I implemented it, not sure there is "correct" or "incorrect" way to do it. I haven't gained any advantages (like performance) with it as well.

5. Where do you get the idea that lines should be sorted? :) Screenshot Android_9.png (look at the "Other" line) clearly states that lines should appear in an order of the data (and checkboxes).