Before you go spending a lot of time trying to develop a UI that would resemble the layout of a Cisco Touch 10, why not think about using the Cisco Touch 10 as the UI??
My personal experience has been split across two paths: (1) develop a UI (on Crestron) that looks like a Cisco UI... until the Cisco UI changes; or (2) develop In-Room Controls (or whatever Cisco wants to name / brand the 'customized controls' feature available) on a Navigator / Touch 10.
With Option (1) you can create very Crestron-customized user interfaces?however you need to be aware that any mimic of a Cisco UI needs managed that it may become out of sync with any Cisco firmware update (and can become a weird conversation between 'user experience' centric audience and 'network security' centric audience). With Option (2) you get no issues with updating Cisco firmware (when the next feature or bugfix is implemented for that system) with the small tradeoff that all user controls now need to fit within the In-Room Control design boundaries.?
FWIW I am a huge fan of option 2 and always lead with that if given the chance.?
