People write all kinds of scripts: many or few scenes, heavy descriptions and/or dense amounts of dialog or light in both, varying amounts of media integrated into scripts. We have developed pagination to allow for faster load times by not waiting for an entire long script to load all at once, instead just several scenes at a time. But the right “several” isn’t the same for everyone all the time as some people’s scenes typically include just a few dozen words and others may have hundreds with multiple files uploaded to each. And, some people’s preferences can be to look at lots of scenes on-screen simultaneously or to control the perspective to a very specific set. So we’ve come up with a mechanism that defaults to showing five scenes at a time, but with a few intuitive controls enables complete customization of exactly what scenes are seen.
Here’s a demo:
Our most recent video.Market7 release also includes a few cool enhancements to the Annotative Player which we’ll get posted to the blog soon.
As we complete intensive focus on converting our next-generation V2 Annotative Player, some focus is being re-directed to it’s pre-production counterpart, our Collaborative Script. Our newest release includes:
Published scripts lay out by page, for faster loading and more control over exactly what’s presented
Dedicated upload window when integrating media into script so that when large files (ex: b-roll) are posted, all functionality of service is available without concern about interrupting upload
Troubleshooting when log-in email address isn’t recognized to accelerate user’s access to service
Further enhancement of V2 Annotative Player including compact “toolbox” access to comment enhancement features
When the storm over Facebook was at its fiercest, fieriest inferno a few weeks ago, allegations were that the company created labyrinthine privacy settings in order to dupe users into maximizing openness of personal content. I sympathized with the company at the time, because availing extensive & intricate capabilities for users, and doing so with coherence are often at odds with each other. But under consistent pressure, maybe merited (although taking a position on that is not the point of this post — staying neutral on that!), Facebook iterated a time or two and came up with the approach shown below. Pretty good! Easy to find settings. Clear what’s being set. The available choices are consistent across selections. Language is concise and plain. For me this coupling of extensive customization with ease-of-use is yet another reminder that in software development, and for that matter in business, greatness gets pursued by reducing apparent dilemmas to becoming false choices.