Graphing looks horrible on iOS and Android phones, slightly ok on tablets and marginally acceptable on Desktops. All the other apps that do "graphing" fake a lot of the output - lots of interpolated lines with smooth transitions that bracket data points to make it all look good...in other words, they are pretty pictures meant to make you go "Ooooooo ahhhhh" but have little connection to reality or add any substantial value. For graphing, one has to always ask - "What is the purpose of the graph?" and "What information is it going to tell me that I don't already know?" In science and engineering, slopes (derivatives) and areas (integration) sometimes tell us things. Interpolation and prediction can also be useful. But in the world of pool management.....meh, they're pretty pictures but don't give much more information than one could glean by simply having the App calculate usage patterns and display spit out the net results, ie, "
Last month you used XX gallons of liquid chlorine which is YY% higher than the previous month and ZZ% more than last year at this time..." That kind of info could be gotten by charting a lot of data points and staring at the graph like a 3D Magic Puzzle or, you could just let the app calculate it and tell you the info.
So the burden is to tell the developer this - what additional information is a graph going to provide that can't be gotten by simpler means and at what cost in terms of App development time, debugging, sleepless night making
@Leebo answer questions, etc, etc.?
(And no, user experience and looking at pretty pictures is NOT a valid response)