diff --git a/content/snacks/app-time-graphs/garmin-steps.png b/content/snacks/app-time-graphs/garmin-steps.png
new file mode 100644
index 0000000..e391379
Binary files /dev/null and b/content/snacks/app-time-graphs/garmin-steps.png differ
diff --git a/content/snacks/app-time-graphs/index.md b/content/snacks/app-time-graphs/index.md
new file mode 100644
index 0000000..fe9c4bc
--- /dev/null
+++ b/content/snacks/app-time-graphs/index.md
@@ -0,0 +1,30 @@
++++
+title = 'Phone App Time Graphs'
+date = 2024-09-09T13:10:36-05:00
+draft = true
++++
+
+In this snack, we look at "value over time" graphs in two different iPhone apps. It's a good opportunity to connect design and task with a comparative critique.
+
+<!--more-->
+
+Here is a graph from the app from my water heater (yes, water heaters have apps nowawadays):
+
+{{<rimage src="water-heater-energy-usage.png" caption="Energy usage from my water heater." attr="Screenshot from the AOSmith app on my iPhone.">}}
+
+Hopefully, the message is obvious: after a month of not using much energy, it started using a crazy amount. Yes, something is broken (the plumber has already ordered a new one).
+
+Of course, there's a Vis lesson here...
+
+My question (or task) is "when did the problem start?" This visualization is not very helpful. To use [critique format]({{<relref "4-critique">}})... if the goal is to help the viewer localize events, having a clear labeling of the axis and easy connection to events would help the user identify the time of events and their specific times.
+
+This graph is the standard choice: we have a measurement over time, so we pick a line graph. But not all apps make this same choice. Here is a graph from the activity monitor in the Garmin connect app (for my watch):
+
+{{<rimage src="garmin-steps.png" caption="Steps per day from my Garmin watch." attr="Screenshot from the Garmin Connect app on my iPhone.">}}
+
+Had the water heater folks chosen this design, it would have been much easier for me to see which day the problem started. There are many different choices in the apps - the Garmin app chose to discretize time, it chose a dark theme, and it chose to encode another variable in the color of the bars. The discretization makes it better suit my task.
+
+Of course, the water heater folks may have had different tasks in mind. 
+
+This is a good opportunity for comparitive visualization (comparing visualizations - as opposed to visualization of comparison). What tasks are each visualization good for? What are the different in choices in each design, and how do they affect the effectiveness for different tasks?
+
diff --git a/content/snacks/app-time-graphs/water-heater-energy-usage.png b/content/snacks/app-time-graphs/water-heater-energy-usage.png
new file mode 100644
index 0000000..5a86065
Binary files /dev/null and b/content/snacks/app-time-graphs/water-heater-energy-usage.png differ
diff --git a/layouts/shortcodes/rimage.html b/layouts/shortcodes/rimage.html
index a9e995e..e6564e8 100644
--- a/layouts/shortcodes/rimage.html
+++ b/layouts/shortcodes/rimage.html
@@ -41,7 +41,7 @@
         {{- with $attrlink }}
             <a href="{{ . }}">
         {{- end -}}
-        {{- $attr | markdownify -}}
+        &nbsp;{{- $attr | markdownify -}}
         {{- if $attrlink }}</a>{{ end }}</p></figcaption>
     {{- end }}
 </figure>