One of the persistent problems in the world of adaptive content is our inability to see how our content will be rendered on different types of devices until the conversion to each device type is complete.
For example, if I create content that is destined for the web, iPad, and Kindle Fire, I really cannot see what that content is going to look like on each device as I write it. Instead, I can only see the content in my editing tool (which, too often, is some random editor embedded into my CMS system).
If I am astute enough and organized enough to use my metadata properly, I should be able to select out pieces of my content to display on the web, another group of pieces from the same content to display on my iPad, and a third group of pieces from the same content to display on my Kindle Fire.
But, how that content is going to look on each device? I can only guess.
In my dream authoring tool (software developers, listen up!!), I can change interface paradigms with the click of a button. For example:
See how it will look in a .pdf. (pretty straight forward)
CLICK!
See how it will look on my website.
CLICK!
See how it will look on my iPad.
CLICK!
You get the idea.
I want my WYSIWYG back. I want to see what I’m going to get, on every type of device, as I create the content. That way, I can modify the content to make it look brilliant on every device, as I write it.
