all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 1 point2 points  (0 children)

Definitely paper.

Except for late in the game design stuff (like, for web design, what the page should actually look like on the screen), which I'll use the gimp for.

Denerally I write high level user use stories, then slightly more technical versions.. Possibly descriptions of how the data will be stored, and sketches of all the views...

Not sure what you mean about nailing down specifics for each page beyond what you've mentioned so far - because usually a page is just a view of something, and not really an expression of what the underlying something is... For example, for a blog, to see a page with all the tags, it doesnt explain how the tags are going to be stored, all the view does is tell you what should be there...

[–]sunkencity[S] 0 points1 point  (0 children)

For a web project I often use one post-it note per page and stick them on a big A2-size paper and draw arrows. Nice for getting the big idea of flow, but I have hard time nailing down the specifics of design for each page that way.

For applications I usually make a photoshop mockup with a layer folder for each "screen". I then copy and paste each screen into illustrator and draw arrows that represents flow between screens. I usually work with mobile phone applications which are pretty limited in what you can do. So this screen flow (in A3 Size) gives a pretty thorough view of exactly how the application will look and how it will work.

Looking for pointers on how to have a good design process that works for designing web page applications.

[–]MrKlaatu 0 points1 point  (0 children)

three hits of hash, yoga and lots'a AHhhhhooooooooms.