Testing and Issues
You can test this app and submit issues during the testing period of the iOS Chart contest.
Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.
Lines are rescaled only on tap release when changing time range. Average speed.
— The app is slow when scrolling.
— The app supports iOS 11+ only.
I have small question (I can ask it in most of works, but we already started our conversation 😅).
In most work (including yours) time ends on 11 pm (23.00) of specific day in ANY timezone. Is it right? I think time should respect time zone where user located.
If I’m wrong, I will remove this comment, because it won’t be issue.
- Value of 130 should definately be slighlty above the 127 line, but it is slighly below in the example (1.PNG). Being accurate with presenting the data is kind of the main point of this whole thing. This has been reported before, this is just another example.
- No arrow on zoom out button (1.PNG).
- The circle of selected point on the chart is too big (1.PNG).
- Lines get clipped around 0 (1.PNG).
- Anamation of range change and max/min change is done in two distinct steps, its easier to do than to animate them both at the same time. (range_animations.MP4, range_animations_2.MP4) The author explains this to be a design choice, I believe it to be not implemented, because its simply harder to do. And this choice leads to poor experience like in range_animations_2.MP4. Sorry to be reporting this like for the 4-th time here.
- No separators above and below chart. (1.PNG) Doing "tableView.separatorStyle = .none" is easy, try hiding separators only where they need to be hidden.
- Values could have been rounded a little prettier (2.jpeg). Has been reported, just another example.
- Some Y values are impossible to read because of their color (2.jpeg).
- 1930 is like way below the 1.9k line, which is truly inaccurate (3.jpeg). Another example, but there clearly is a problem, in spite the author trying to talk his way out of it.
CA Profiler is very good at measuring performance in most cases. The only thing you need to do is doing your actions continuously.
Your animations may look smooth enough for you, but if your solution is not performant enough you will see objectively low fps in profiler.
When you use standard drawing techniques you get less bugs and standard performance (not good enough for this contest).