…do you piece it out into several prototypes, one per section or feature? This is how I currently do it and was curious how the single prototype approach works out. Seems like it may get bloated and slow.
Where am I?
In UXPin you can ask and answer questions and share your experience with others!
It depends on the stage of the product, and the use of the prototype. In most agile teams, prototypes are scrapped and started over at the start of a new sprint Understanding the lifespan of what you are creating is also key. Prototypes don't live forever. :)
Each prototype has a specific purpose and learning agenda. Sometimes its a small part of an experience, sometimes a full experience is built and linked across multiple protos, and sometimes it' all in one.
The more interactions you stack to simulate arrays or processes (canvas or element) will affect your page speed.
Since posting this, I've decided that putting it all into one prototype would be a terrible idea. :-)