diff --git a/Documentation/applications/examples/baromonitor/baromonitor.png b/Documentation/applications/examples/baromonitor/baromonitor.png
new file mode 100644
index 00000000000..2026ecb47ca
Binary files /dev/null and b/Documentation/applications/examples/baromonitor/baromonitor.png differ
diff --git a/Documentation/applications/examples/baromonitor/index.rst b/Documentation/applications/examples/baromonitor/index.rst
new file mode 100644
index 00000000000..f73b4140902
--- /dev/null
+++ b/Documentation/applications/examples/baromonitor/index.rst
@@ -0,0 +1,28 @@
+===========================================
+``baromonitor`` Barometer Dashboard Example
+===========================================
+
+This example is used to demonstrate a practical use case for an LVGL application
+on NuttX. It subscribes to a barometer sensor topic and displays the pressure
+and temperature information on animated gauges.
+
+.. figure:: baromonitor.png
+   :figwidth: 70%
+   :align: center
+   :alt: The barometer dashboard in action
+
+   The barometer dashboard in action
+
+To use the barometer dashboard, just ensure there is a ``sensor_baro`` topic
+registered on the target and then run ``baromonitor``. These sensor topics are
+registered by NuttX barometer sensor drivers (see
+:doc:`/components/drivers/special/sensors/sensors_uorb`).
+
+By default, the application attempts to subscribe to ``sensor_baro0``, but if
+you wish to monitor a different barometer topic you can pass the instance number
+as an argument (i.e. ``baromonitor 2`` subscribes to ``sensor_baro2``).
+
+For maximum compatibility with all sensors (those that publish on their own via
+interrupts/kernel threads _and_ those that only fetch data when read from), the
+application takes the approach of reading sensor data in a loop at a rate
+defined by ``CONFIG_EXAMPLES_BAROMONITOR_SAMPLERATE``.