Except mock-ups != prototype.
Picky, picky.
I'm picky because, as a coder, I have to personally deal with different variations of what people think "prototype" means.
One client thinks prototype means "mock-up", another thinks it means "ready to go" after a round of QA.
Surely you can see how this might effect a project overall?
No doubt. That's why specifying project requirements and writing proposals is usually so important for both client and coder. Managing expectations is key.
Apple designers come up with 10 entirely different mock ups of any new feature. Not, Lopp said, "seven in order to make three look good", which seems to be a fairly standard practice elsewhere. They'll take ten, and give themselves room to design without restriction. Later they whittle that number to three, spend more months on those three and then finally end up with one strong decision.
[Source: http://www.businessweek.com/the_thread/techbeat/archives/200...]