As far as I have seen, generally speaking, in projects other than web or blend, the reuse of prototype code is relatively rare. And the prototype that pursues code reuse must already be at a relatively high fidelity stage, and it is no longer in line with whatsapp Database the purpose of rapid prototyping to pursue quantity and iteration, which will be mentioned below. When facing external customers, the visual fidelity of the prototype will be more important, it can better help customers whatsapp Database understand the design, and a prototype with high visual fidelity will be more convincing when making proposals. The disadvantages are also obvious.
The same prototype requires more time investment, and more time is invested once the design is changed; and in the early stage whatsapp Database of the project, it is generally difficult to make a prototype with high visual fidelity, so in the entire design process applications are also limited. Therefore, if it is not necessary to propose proposals to external customers, but only for internal communication and inspection of interaction problems, the fidelity of vision can whatsapp Database be a secondary consideration, with the fidelity of interaction as the main dimension. Speed and quantity should be pursued.
As much experimentation and iteration as possible in the early stages of the product, in order to discover new ideas and reduce risks later in the project. So I define rapid prototyping as: the early stage of a project, the act of prototyping whatsapp Database with the main purpose of discovering new ideas and testing designs. About the pursuit of quantity, insert a short story, read from Bill buxton's sketching user experience book: The pottery teacher said on the first day that the students would be divided into two groups, the students sitting on the left in the studio would be whatsapp Database graded only on the quantity of pottery they made, while the students on the right would only be graded on the quality of the pottery they made.