Comments on: SpoolCast: Roughing it with Interactive Prototypes

By: Web App Expert Interviews - Part 1 » UIE Brain Sparks

Web App Expert Interviews - Part 1 » UIE Brain Sparks — Tue, 12 May 2009 19:00:52 +0000

[...] More details on Richard and James interview. [...]

By: UXA: SPUD - The Lean Agile UX Process « Tales from a Trading Desk

UXA: SPUD - The Lean Agile UX Process « Tales from a Trading Desk — Thu, 30 Apr 2009 04:16:07 +0000

[...] SpoolCast: Roughing it with Interactive Prototypes [...]

By: Spoolcast on Beyond Deliverables / Prototyping | UX Agile

Spoolcast on Beyond Deliverables / Prototyping | UX Agile — Sat, 21 Mar 2009 11:57:17 +0000

[...] recent podcast with James Box and Richard Rutter visits some of the notions I expressed in the post “UX Design Artifacts: Conversation Anchors [...]

By: Bob Hotard

Bob Hotard — Fri, 13 Mar 2009 07:01:10 +0000

I’ve worked with Bo Lora on this integrated prototype and what sets it apart is the syncranization of Requirements, Technical & Testing specs all integrated with the UI design of the interactive page. To really succeed in corporate web design, you must address all these areas of a site in order to efficiently meet the demands of the business.

By: Bo Lora

Bo Lora — Thu, 12 Mar 2009 20:54:26 +0000

I’ve been doing this for years. In addition I use a way to attach technical specs via an external xml document. This is useful when working with a technical analyst so they can work ahead while the prototype is being worked on.

By: Umair » Blog Archive » SpoolCast: Roughing it with Interactive Prototypes

Tue, 10 Mar 2009 06:19:34 +0000

[...] Here is the original: SpoolCast: Roughing it with Interactive Prototypes [...]

By: Ben Chinn

Ben Chinn — Sat, 07 Mar 2009 00:07:24 +0000

I’ve been developing interactive HTML/CSS/JS prototypes as part of the development of a web application and it’s been extremely helpful. Stakeholders love to get hands on with this kind of prototype and can give meaningful feedback. Developers don’t have to create all the markup from scratch since the HTML framework already exists in the prototype. Best of all, interactive behaviors can be communicated with near perfect accuracy.

This has been a great solution for me mostly because I can work fast with the technology, so this isn’t much harder for me than mocking up purely visual prototypes. For those who are slower with markup or better at communicating ideas visually this may not work as well as it has for me.