HTML Wireframes and Prototypes: All Gain and No Pain

Home > Archives > 2003 > January > 10 > HTML Wireframes and Prototypes: All Gain and No Pain

« Microsoft's wireless data network: 20-year-old technology and applications · Contain the Idea Virus »

"What I call an interactive HTML prototype goes a step further by linking navigation on an HTML wireframe to other wireframes representing subsequent screens, filling in content as needed, and adding mock functionality such as drop-down menus and fields that dont tie into any backend."

Exactly. I use HTML wireframes every time I need to spec anything complex, simply because you can fire up the browser and click on them (yes you can create hyperlinks with Powerpoint but that really doesn't feel like using a web site) and mimic actual user behavior. I started doing that when I had to create an advanced search engine for real estate listings. I could easily detect what was wrong with my early trials and improve the flow from screen to screen, based on feedback from coworkers and the client. Non-HTML prototypes don't feel nearly as real because of the lack of interactivity.

9/19/05 update: Comparing deliverables (static vs. HTML wireframes).

Category(s): building online products ·

Name: Email Address: URL: Remember personal info? YesNo	Your e-mail address is used to send you future comments to this entry, but I won't use it for any other purpose and it won't appear on the site. I prefer you comment using your real identity, thanks.

Email this entry to: Your email address:	This form is used only to email this story to your friend. I won't save the email addresses you type in, or use them in the future in any way. Message (optional):