Skip to content

High level development priorities

Charles Forman edited this page Jun 3, 2014 · 2 revisions

It's important to understand the priorities of this tool. The mission is: to make the best way to visualize a screenplay possible.

1. Ease - First and foremost, people need to be able to create as nearly as fast as they can think. While impossible, every step closer to this makes the creative process better.

  1. UI - Remove complexity in the UI. Put UI where is contextually relevant. Remove superfluous views.

  2. Functionality - Better writing tools, better drawing tools.

  3. Importability - Bring in data from other formats: paste in, script from final draft or pdf, music?

2. Get data out - In a creative system, the process is usually contained in a vacuum and is only as valuable as what you can get out of it.

  1. Widest reach (PDF) - Way to export data for the widest / safest possible reach

  2. Most technically tangible (Files and Folders) - Through an open file standard, the data can be transformed using other tools, or tools to be created.

  3. Most functionally accessible (File app packages) - Have the app create self contained javascript sites to export the data for view by anyone without the app. (Script breakdown / animatic / etc)

3. Collaboration - Collaboration is inevitable in the creative process. The tool should be aware and embrace the idea.

  1. Track changes - Ability to see who did what.

  2. Realtime editing - Ability to work with multiple people at the same time.

  3. External breakdown submissions - Ability to have metadata added by none creatives in an approvable fashion.

4. Analytics - Managing lots of data is a thing a human doesn't do well. Tools should attempt to provide clarity around quantitative things.

  1. Stats - Quantifiable stats from the macro to the micro

  2. Guides / Warnings - based on stats provide guidelines

  3. Alternate views - a different way of looking at things often provides more clarity.