diff --git a/doc/devices_classes_branch.txt b/doc/devices_classes_branch.txt
index c92dca8..a7c9203 100644
--- a/doc/devices_classes_branch.txt
+++ b/doc/devices_classes_branch.txt
@@ -429,6 +429,38 @@
 when_updated callback)
 
 
+---- BETTER DEMOS
+
+Especially when testing without hardware, there are a few variants of things
+to test. Really do want the demos in the top level directory to be
+simple and representative of what a first time user might do with the code
+
+1. legacy switches
+- learn mode for legacy switches (learn mode with a broadcast tester)
+- turning legacy switches on and off
+
+2. mihome monitoring
+- discovering and registering mihome monitor devices into your registry (learn mode/tester)
+- generating an energy log from mihome monitors
+
+3. mixed monitoring and control
+- creating simple logic that turns mihome switches on and off based on energy usage/timer
+- perhaps also turning legacy switches on and off based on energy from a mihome monitor
+- showing the device agnostic oo interface for any switch device
+
+Perhaps there is a commissioning app, that allows
+- learn mode broadcasts for legacy devices
+- testing legacy device switches by turning on and off
+- assisted join from mihome with add to registry with friendly names
+- showing trace of data coming from mihome monitor
+- turning adaptor plus switch on and off
+
+It could just be a simple menu system.
+This then means you don't have to have all this in the demo apps
+and the demo apps can just refer to object variables names
+from an assumed auto_create registry.
+
+
 ---- HARDWARE TESTING
 
 Test with real radio