Thank you for your thoughts. Since the app itself doesn't have users yet I think it might be overkill to start discussing the configuration on its own git repo!

Thank you for your thoughts. Since the app itself doesn't have users yet I think it might be overkill to start discussing the configuration on its own git repo! However I will take everything you wrote into consideration and I appreciate the time you took to respond. I especially liked the clarification about screen space, which I'll use to ensure I don't nest things more than 1 max 2 levels. By the way, although it is too much to open a repo for it, what do you think about this UML for how I structure the parts of the application? https://imgur.com/a/FUTphwa https://imgur.com/a/FUTphwa (I already have the parts working.) The user talks to the voice recognition engine which is a subprocess of the voice recognition server. In terms of what to do (actions to take) the voice recognition takes configuration files and dispatches scripts. To give feedback to the user the voice recognition server also communicates via a web interface. (i.e. the user could have this web interface open and see what actions the home automation server is taking, which scripts have been launched etc.) Do you think this structure is all right for a configurable voice recognition automation server app?