I am designing an interface and I currently have about 25 Pages, but the Pages palette is becoming burdensome to use (pages are too big in the palette to see many at once) and for various reasons I'm thinking States might be the better way to go. I will probably have at least 25 more static screens to present in the end, for a total somewhere between 40-70. I need to export these as individual pngs which I will show by dumping into a network folder with a php file in it which will let me click through each screen (this part is already built, I don't need Fireworks to create this interactivity).
Which feature should I use, Pages or States? I need to show how the user will navigate through several different pages, and on each page there are various controls, and I need to show different progressions in the interface over time (for instance, when the user has been using this UI for one day, two weeks, and three years). I'm using symbols for elements like header and footer, I know about Master pages, and I'm now very comfortable using the share layer to pages feature to share layers across pages. I'm not using any hotspots or rollovers; the presentation will be a linear clickthrough of static images.
I have read all the articles I can find (including Using Pages and States in Fireworks CS4, Industry Trends in Prototyping, Maze of Pages/States/Layers simplified) and watched several videos (including Creating Interactive Prototypes, Creating interactive prototypes for reviews, and Cooper Journal: How we use Fireworks).
Can anyone give me a solid reason for using or not using States? My UI won't have any "animations" but I do want to show what changes when a button is pressed, for instance. Thanks!
Okay, it's been about five months and I have developed what I assume is common practice for interaction designers who use Fireworks to create mockups for multi-page or multi-view on-screen experiences (websites, computer software, mobile sites or apps, etc.). For anyone else who's curious, here are the steps I now take to manage assets across pages in Fireworks. Not news to the old-schoolers, but perhaps there's a newbie or two out there who has searched for but not found the info they want on how to organize a Fireworks file.
Hopefully that helps someone. Please reply to this post if you have better ideas.
Oh, and I solved the problem of pages being too big in the pages palette by choosing "no thumbnails" from the thumbnail options within the pages palette. Right click on any page and choose "Thumbnail options."
And I've also abandoned the idea of showing button states. Maybe someone has a better way of dealing with this, but for me showing the states became less important.
Europe, Middle East and Africa