This link has been bookmarked by 45 people . It was first bookmarked on 08 Mar 2006, by Joel Liu.
-
16 Aug 11
-
29 Jun 10
-
19 Mar 10
-
17 Mar 10
-
27 Mar 08
-
20 Dec 07
-
20 Nov 07
-
05 Aug 07
-
11 Jul 07
-
15 Apr 07
-
04 Apr 07
-
01 Apr 07
-
25 Feb 07
-
wireframes
-
-
06 Dec 06
-
04 Nov 06
-
25 Oct 06
-
14 Sep 06
-
15 Aug 06
-
09 Aug 06
-
11 Jun 06
Are Halland"HTML prototyping and full-on agile development of Web applications are increasingly viable options that help minimize communication gaps and assumptions and deliver more accurate results sooner." (Garrett Dimon - Digital Web Magazine)
-
16 May 06
-
12 Apr 06
hmbhmbSays: go into HTML soonest, because it is real and paper isn't
-
Many variables get overlooked when creating wireframes or other paper documents. Factors such as state, security, error messages, level of effort, page flow, DOM scripting and other dynamic elements can be ignored or misrepresented.
-
-
11 Mar 06
-
08 Mar 06
-
As a result of the misconception that prototyping is throwaway work, you’ll often hear that it’s faster or easier to create a wireframe or other document than it is to actually write the HTML, CSS and JavaScript. In this case, that’s a fairly accurate statement. However, the real reason that it’s faster is because it ignores factors that can have a signifi
-
On a related note, if you’re really worried about throwaway effort, you might want to take a moment and think about what happens to those detailed design documents when the project is over. If nobody ever looks at them again, then you’re already doing throwaway work. Why not just spend that time going straight into building your interface and simply work from basic sketches instead of deliverable-quality design documents?
-
You need to temporarily suspend any notions that prototyping is always throwaway work. If you approach it as throwaway work, it will be. However, if you approach it with the intention of keeping it, you can create modular code that can be reused.
-
Chances are, you use some sort of prototyping to illustrate Web interfaces for clients and stakeholders, and rely on those prototypes for approval. Whether you’re using visual design comps, wireframes, site maps, process flows, page description diagrams (PDDs), or a combination of these, your goal is always the same. You want to mitigate the cost of making changes.
-
-
07 Mar 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.