ANN: Warfel's book "Prototyping: A Practitioner's Guide" now available

17 Nov 2009 - 11:49am
4 years ago
1 reply
1239 reads
Louis Rosenfeld
2007

(apologies for cross posting)

It's a pleasure to announce that Todd Zaki Warfel's book, *Prototyping: A
Practitioner's Guide, *is now available for purchase. In just under 200
pages, Todd provides a hugely practical take on a hugely practical topic,
and shows you how to prototype using approaches both low-tech (e.g., paper)
and high-tech (Axure and Fireworks). So please:

- read the wonderful testimonials:
http://rosenfeldmedia.com/books/prototyping/content/testimonials/
- check out the lovely illustrations on Flickr:
http://rosenfeldmedia.com/books/prototyping/content/diagrams/
- and then buy it directly from Rosenfeld Media:
http://rosenfeldmedia.com/books/prototyping/

*Prototyping *is available in two packages: a full color paperback plus a
screen-optimized DRM-free PDF, and a digital package (two DRM-free PDFs:
one screen-optimized, and one for printing yourself). An EPUB version is on
the way as well.

Thanks for considering it, and thanks especially for spreading the word.

cheers

Louis Rosenfeld :: http://louisrosenfeld.com :: @louisrosenfeld
Rosenfeld Media :: http://rosenfeldmedia.com :: @rosenfeldmedia

Comments

20 Nov 2009 - 1:48pm
David Scharn
2007

Hello all,

I just finished reading Todd's book. It's a great resource for learning how to use tools at hand to build interactive prototypes. (Catalyst and SketchFlow are a different conversation.) We might consider PowerPoint, Visio, Fireworks and the others (except Axure and HTML) for wireframing, but we don't usually think of them for building interactive prototypes.

We typically expect to use a book like this as a reference, to be picked up when we have a problem to solve, like figuring out how to prototype in PowerPoint. But the book is truly engaging. I read it straight through. I especially like the guidelines for the prototyping process and the eight guiding principles. These help us structure a method for prototyping. They all make sense and are points we already know (we say, yes, of course), but outlined like this they provide tangible direction and boundaries for the work.

With each chapter that describes a prototyping tool, I found myself saying, "Yeah, I can't wait to try prototyping in that," and I'd say it again in the next chapter. This even happened reading the chapter on HTML, and I'm no coder.

The GUI components, templates, and articles that Todd points readers to are worth the price of the book. Actually, they're worth more. I've often spent hours - sometimes days - trying to track down resources like these. Sometimes I find them, other times I don't. Having these references handy is a huge time saver.

One constructive observation: I think the section on Progressive Reveal should be pulled from Chapter 11 (HTML), as this is a general lesson in "best practices" for UI design, similar to the guiding principles. All readers would find this information valuable, but those that skip the HTML chapter might miss it.

Cheers,

David Scharn

Syndicate content Get the feed