thank you for your reply.
As far I can say, the concept of template here is most bonded to two things: the devices that we will use for control (iPhone, iPad, Android and PC) and the controlled devices (KNX, X10, Z-Wave, etc.).
The first objective should be to make a template library of every devices supported by Open Remote, including all sensors, sliders, switch and commands required to control the specific device. Then, a minimal graphic panel would complete the device's configuration, so it's ready for a basic usage. For example, I'm making a panel for k8055 board that includes all requirements for its control, as soon as it will be ready I will share the panel on the pubblic area of the Designer so everyone can load the template and everyone is ready to go to use it. This make more sense for the community.
In a second instance, it could be important to have only graphic templates because they reflects the final product. A product is not a device! A product should be compliant to the customer needs and could use more kind of devices.
In conclusion, the best thing would be that everyone can choise to save the device template, the panel template or the two things together. Obviously, the Designer should also expose a function for the template loading (for device or panel) by adding each one to the current Designer project.
That way a system integrators can build its product (not the device), simply by loading the templates that he/she needs.
On the other side, graphic agencies and graphicians can do their business by building graphic panels for final products. So, a system integrator with not graphic ability can buy panels from the market, attach it to the desidered devices and sell the final product (or solution).
This is my thought.