I haven't researched it yet, but it would be surprising if there's not a way to make fancy charts from the Particle API using IFTTT or something. I've seen Blynk and Adafruit.io charts and gauges, but usually those are for one variable at a time. To me, infographic type designs that organize a lot of related information into a small space--think Edward Tufte--are more interesting than gauges or single variable graphs.
Fair warning, this is a bit of a rant, and it's as much or more about my feelings on the general state of things with on the OpenAg as it is about your specific question.
Anyhow, I think it comes down to us having different goals, assumptions, and biases.
Here are some of mine:
I'm not comfortable thinking about this exclusively from the perspective of what's useful or interesting to privileged, wealthy people in well connected cities with reliable power. For some context, see this thread http://forum.openag.media.mit.edu/t/openag-in-low-middle-income-countries/1914/3. Also, this: https://blogs.lt.vt.edu/thereeltara/2016/09/15/understanding-privilege-implicit-bias/. As an example, real time monitoring can be done with an LCD or indicator lights. Using USB serial to an Android phone might also be a realistic scenario. Anyway, the bigger problem is implementing control algorithms that do their jobs reliably without much intervention.
I'm concerned about what I hear of modern medical research on the negative effects of EMF on mitochondrial function, fertility, etc. The idea that EMF can be dangerous isn't controversial (check the FCC's amateur radio exams), it's just a matter of what power levels constitute a problem. Considering how people used to feel about DDT, I'm not inclined to trust that current standards for acceptable EMF exposure levels are safe enough. Completely avoiding wifi these days isn't practical, but we can moderate our use of it. If nothing else, being conservative about using wifi makes the system more robust and is a step toward relevancy to off-grid battery powered greenhouse controllers.
I prefer things that are engineered to be simple, robust, and efficient. It bothers me to see people build stuff that profligately wastes computing power or other resources. Building cheap junk that just breaks is also not good. I see both as signs of carelessness in not taking the time to understand the problem domain, not learning to think with clarity and discipline, not taking time to learn how to use appropriate tools well, and not using good judgement about costs and benefits. Being sloppy about wastefulness and lack of due care is how we got into the current climate mess, among other consequential problems. TL;DR doing more with less is a virtue.
I don't see that it obviously makes sense to couple image collection with basic environmental controls and data logging for environmental sensors. I've collected a few GB worth of Raspberry Pi plant time lapse pictures now, but they haven't done me much good. The time lapse movies I made were kind of fun to watch once or twice, and I learned a bit from that. On the other hand, the sensor charts give me actionable information that was useful on a daily basis for keeping the plants healthy. An automatically controlled fan would have made real time charts a luxury rather than a necessity.
People who want images could use a Rasbperry Pi camera, cron, raspistill, rsync, etc. independently of whatever they do for sensing and actuation. Or, if they want higher quality images, just hold a neutral density filter in front of a phone camera. My iPhone pictures came out way better than my Pi camera pictures.