This link has been bookmarked by 63 people . It was first bookmarked on 17 Jun 2008, by Mr. DiGi.
-
13 Jan 12
-
First, prototyping processes foster collaboration. They often require designers and developers to work closely together on tangible output in a short timeframe, getting the right people in the room communicating. Second, designers and developers start to understand what is possible.
-
-
10 Jan 12
-
25 Jan 11
-
Ultimately, the audience can affect how polished a prototype needs to be. If a prototype is just going to be passed among the design and development team, you can probably rely on a shared understanding of what is significant. On the other hand, if you are presenting the prototype to stakeholders or decision makers that are not involved in the actual development, you may need to explain what is “real” and what isn’t
-
Fidelity can be a problem
-
Remember part of the reason the proponents of Agile Development look askance at documentation is that they want to stay focused on building the actual product.
-
use the quickest and most lightweight method that gets you the results you’re after
-
-
21 Dec 10
-
13 Aug 10
-
25 Jun 10
-
23 May 10
-
-
increased collaboration
-
increased collaboration
-
increased collaboration
-
Ajax and rich internet applications (RIAs). Before
-
-
19 May 10
Derek ColandunoI’ve noticed more and more conversations about prototyping as a method of approaching web application development.
article code coding design prototype webdev webdesign programming usability web documentation development process wireframe
-
06 Jul 09
-
19 May 09
-
28 Apr 09
-
04 Apr 09
-
06 Mar 09
-
04 Feb 09
-
14 Dec 08
-
12 Dec 08
-
10 Dec 08
-
21 Oct 08
-
13 Aug 08
-
12 Aug 08
-
29 Jul 08
-
22 Jul 08
Joaquim Rendeiro«I’ve seen countless hours spent generating thousands of pages of documentation that were never used. This in itself wouldn’t be so undesirable if we had infinite developer resources. »
-
12 Jul 08
-
05 Jul 08
-
04 Jul 08
-
01 Jul 08
KurtFirst, prototyping processes foster collaboration. They often require designers and developers to work closely together on tangible output in a short timeframe, getting the right people in the room communicating. Second, designers and developers start to
-
30 Jun 08
-
22 Jun 08
-
Ludo VangilbergenSo where does prototyping fit in the development process? Well, it can be used appropriately just about anywhere. Think of sketching. Drawings, from quick back-of-the-napkin pictures to fully-realized drafting diagrams all fit under the umbrella of “sketching.” Similarly, there are a variety of prototyping approaches, from really quick low-fidelity methods to fully realized working mock-ups. It is important to
-
19 Jun 08
-
18 Jun 08
-
However, if the prototype is used as a deliverable and the original team is not accessible, some explicit thought should be given to conveying this type of information as well
-
-
-
17 Jun 08
-
-
Users can request features they “need” only to discover when using the new application that the feature in question was not actually helpful.
-
-
Frederik Van ZandeOver the last year, I’ve noticed more and more conversations about prototyping as a method of approaching web application development. Beyond casual conversations, prototyping has also increasingly been the topic of blog posts or subject matter for conference presentations. The reasons for this increased interest include a laundry list of benefits that prototyping can bring to the process of developing compelling web applications. Ranging from increased collaboration to more effective solutions, these benefits have made prototyping a valuable new approach to consider for your next project.
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.