I recently participated in a presentation at Dscoop Phoenix with three companies that I've known for over a decade: Pageflex, XMPie, and Marcom Central. We had joined a "Composition Engine Panel Discussion" with web-to-print luminaries Jen Matt (of web2printexperts.com) and Chris Reisz-Hanson.

It was quite an honor to be on this panel, but an even greater honor has been the opportunity to work with these companies' rendition technologies since they first came on the scene. I have been involved in solutions involving all four technologies, and I've met the developers critical to the success of the underlying rendition codebases. These range from: FusionPro, the composition engine under Marcom, which dates from the 1980s; to PageFlex, the PDF rendition library from BitStream also originating in the 1980s; to InDesign, dating from the late 1990s. InDesign is the engine that we and XMPie use - it was created in part by our staff.

I was thankful to attend Drupa 2016 and spent most of my time in Halls 7 and 7a looking at the range of online editors from around the world. The following five online editing solutions stood out for me from among the 15 or so that I explored.

In this post I am going to explain how Silicon Designer is built to support the most demanding online editing solutions in the world. We are at a point in the evolution of this product that I am truly proud of, and I am deeply grateful to our incredibly talented developers and other participants in its success. Go here for some history of how it came about: in this post we will talk about what it is and how it works.

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

Recent Posts