Just like a standard "content app" can be created with configuration alone, it should be possible to create a standard "simple configuration app" with configuration alone.

This is another common use case for apps which we could make much easier.
Being configurable would make them easy to implement by "light developers", ie non-java devs or projects using light modules.

As a user, if I opened such an app, the config subapp would be displayed.
The config subapp would look something like the mail app, (or a typical DetailSubApp) and would simply display a dialog and its actions.

It could be configured just like a standard DetailSubApp.
Developer could configure the workspace and node where the values from the form should be saved as properties. (Perhaps the existing contentConnector works for this.)

An additional benefit to someone using a standard magnolia dialog rather than a custom vaadin form is that they could take advantage of the validation, the helptext, and the saving of the data to jcr that Magnolia provides.