 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
I start all Flash projects with detailed storyboards (shown throughout the folio samples). Frankly, I think going into a Flash project without a storyboard is like trying to make a movie without a script, or cutting your own hair in a darkened room. The project will get done eventually, but it's probably not going to be what you hoped for.
Because of the time involved in developing Flash projects, it's important for everyone who has a say in the project to approve storyboards prior to production. The storyboards can be anything from small, 4 panel pencil sketches to full size Photoshop illustrations. Bottom line, it's important to have a reference of the goal before producing a Flash piece. In many cases two or three versions of storyboard development can save a surprisingly large quantity of money, while improving the quality and bolstering expectations of the final piece.
Too many people, bless their hearts, want to deliver their content in Flash for the wrong reasons - they see it as the cool thing to do. I, though, feel pretty strongly that it should be used to deliver web content only if the timing, motion and interactivity are truly needed and warrant the cost of development. In other words, do you really want it? Is it worth it? Is it truly usable for your customers (and for search engines!). For many clients and purposes, its more appropriate to deliver web content using more standard HTML. Eight times out of ten you'll get more return on your investment if you put more of your web budget into writing great text and scalable back end features.
Not discouraged yet? Good. Just one more thing to consider - typically Flash content is difficult and expensive to update. However, that's fixable. I can build updatability mechanisms into the Flash architecture.
All that said, if you decide Flash is right for the project, you can be confident that I'm deeply in tune with the download characteristics and capabilities of Flash sites. By using detailed compression techniques and best practices from day one of the project I make Flash content (and ALL web content) as small as possible while keeping a rich end result.
When we start a project I'll create a password protected site for you on goldmanDesign.com. Only you can view this site. It's the place we'll go to review your designs and documentation, download files and in general keep in tight communication about your project status and progress.
