Our design process goes something like this: create mockups in Illustrator and Photoshop, typically a screen shot of the home page and a secondary page or two. Maybe an “over” state or two to show interaction, although usually not. Get approval from client, then toss over the wall to the programmers. They ask for overstates. Create them. They ask for more images. Create them. They need a layout for some interactive form, for a thank you page, for a 404 page. Emails fired back and forth. They send the beta site over for review when they’re finished. It doesn’t behave quite like how the you envisioned; somethings are broken, some things act strangely, you think they might have taken it upon themselves to design their own states or layouts because they got sick of the back and forth.
Let’s face it, no one is happy in this situation, a lot of time is inevitably wasted, and the end result is not what the designer envisioned in the first place. I’ve managed to extract myself from this situation from designing and developing in Flash, the ultimate playground for a programmer-designer hybrid like myself.
The problem with this process is that the designers, who are trained in print design, are completely removed from the interactive design process. Creating the flow, the animations, the experience of a website should lay with the designer, not the programmer. But let’s face it, not every designer should or wants to learn to program. So what does it mean for a designer to do rapid prototyping? A prototype is not the design of a screen shot, it’s a working, clickable page that actually shows the interaction that the user will go through. It may just be HTML with latin text, but it similates the experience. So how does a designer create this without learning HTML?
Adobe has a few tools that are aimed at this very process. One of them is the very mysterious Fireworks; while I have had Fireworks for years, I have never actually used it, and it seems really complicated. According to Adobe, here is the feedback on the CS4 version:
Existing Fireworks users love the workspace improvements, specifically the ones that help them quickly prototype and design web pages and applications. And newer users, especially those who are familiar with Adobe Photoshop and Illustrator, find the improved user interface more approachable and intuitive.
There is an interesting article on Adobe’s site about prototyping.
Prototypes also provide extremely valuable insight into transitions between state and more dynamic interactions. Interactivity is about behavior—how a product or artifact changes over time in response to user input and events in the world.
Adobe’s website also have a ton of instructional videos on it, none of which will stream for me, in any browser. So I’m just going to play around and see what happens.
- I found an old design comp I did in Photoshop a long time ago. First a create a new document in Fireworks. Then I import my PSD, and I am confronted with a window that asks me what size I want the file to be. It’s nice to know that I can easily resize my file, but it’s a bit confusing, since I designed it at the size I want it.
- Then I get a weird tool that is simliar to the paste-in-place tool in inDesign. Not really sure why…because I already said what size I want my file. I am confused. I don’t think this ended up the right size.
- I right-clicked on some text to turn into a clickable link. Convert to symbol, button. I see properties/symbol properties panels at the bottom. You can specify the link, alt, text, style, target, the export type and file name. Looks pretty straight forward.
- I created a new page in the page panel; looks like a completely seperate page/file (I lose all my layers)
- I creeated a new state, and my slice for my button is still there, but again my layers have dissapeared. I’m not sure if this is supposed to be like a “down” state for the entire page or what. OK, double clicked my button, and I see within the button are the state layers (reminds me of making button in Flash, also similar to making animated GIFs in Photoshop).
- I tried just exporting HTML and images from here, and the link is an image, but its black when I rollover it. Considering I only had Fireworks open for about 5 minutes, I’m feeling pretty good that I made a button and exported to HTML, although its far from workable at this point.
Another tool I have been eyeing is Flash Catalyst (used to be called “Thermo”).
Adobe® Flash® Catalyst is a new professional interaction design tool for rapidly creating application interfaces and interactive content without coding.
From their little demo video, the designer creates their normal static page in Illustrator or Photoshop, imports it into Catalyst, and then can simply click on groups and shapes and create buttons. Unlike importing artwork into Flash, the Catalyst has the same tools as Illustrator (I think?), and maintains layers and generally looks identical. From the looks of it, this tool is aimed at designers passing things off to Flex developers, as the end result is a SWF or AIR file. I’m not sure how well it work work to prototype HTML, but it looks pretty slick for Flash.
The point of all this is simple: design in your real medium. Creating an Illustrator drawing and handing it over for programming is a lot like creating a sketch in pencil and handing it to a painter. Chances are it won’t look anything like what you intended. And even if it did, most of the process of painting is in the handling of the paint; you start with one idea, and it evolves and changes as you work with the medium. Even if you know nothing about programming, take a step towards learning a bit or using a tool to help you with the process so you can design with your real medium. You might just find yourself with a whole new source of inspiration and ideas.
K Design, Process, Prototyping