For seven years, our Silicon Designer product has expanded in use, across many countries, languages, and use cases. From B2B applications where franchises easily manage brand collateral, to some of the largest consumer-facing document personalization sites on the planet, our product has proven itself to be solid and reliable, yet also very extensible. It is integrated with numerous forms of shopping cart, DAM system, workflow system, and database, and it has diverse forms of User Interface:

no two Silicon Designers look the same!

Making it easy for our clients to customize their unique implementations has been our top priority. We have found that web standards, implemented correctly, make all the difference.

As more and more organizations implement web-to-print workflows that meet their ever-changing business demands, they often find that customization of their chosen solution is a must. Yet with HTML5 based solutions, this customization layer can be a significant challenge. This is due to the vastly different ways in which software vendors decide to combine the overlapping technologies.

Silicon Publishing co-founder and CEO talks of Silicon Publishing's origins, where they are today, and where they are headed in the future in this interview with Superb Crew.

We at Silicon Publishing have come to specialize in developing online design applications, with years of extensive work building web-to-print solutions based on InDesign (yes, pre-server) and Adobe InDesign Server. Because we didn't start with a product, but spent our first 9 years as a custom development shop, we have not tended to guide our customers on UI but have typically let them define what they wanted.

When we did create a product, Silicon Designer, we focused on the core common layer of what we had built for solutions, keeping in mind that the user interface would have to be quite different for different clients. We continue to see that different companies have wildly different concepts of what is important, even given similar document types/workflows, and there are differences between document types and business context that will in many cases require different UI approaches. We are glad we worked so hard at keeping the core functionality flexible with respect to user interface. Following are five UI considerations we see as we build online design tools.

1